Merge "Merge 'android-3.18.105' (20653d92) into 'msm-3.18'"

Contact:	"Sheng Yong" <shengyong1@huawei.com>

Description:

		 Controls readahead inode block in readdir.

What:		/sys/fs/f2fs/<disk>/extension_list

Date:		Feburary 2018

Contact:	"Chao Yu" <yuchao0@huawei.com>

Description:

		 Used to control configure extension list:

		 - Query: cat /sys/fs/f2fs/<disk>/extension_list

		 - Add: echo '[h/c]extension' > /sys/fs/f2fs/<disk>/extension_list

		 - Del: echo '[h/c]!extension' > /sys/fs/f2fs/<disk>/extension_list

		 - [h] means add/del hot file extension

		 - [c] means add/del cold file extension

- ti,palmas-enable-dvfs2: Enable DVFS2. Configure pins for DVFS2 mode.

	Selection primary or secondary function associated to GPADC_START

	and SYSEN2 pin/pad for DVFS2 interface

- ti,palmas-override-powerhold: This is applicable for PMICs for which

	GPIO7 is configured in POWERHOLD mode which has higher priority

	over DEV_ON bit and keeps the PMIC supplies on even after the DEV_ON

	bit is turned off. This property enables driver to over ride the

	POWERHOLD value to GPIO7 so as to turn off the PMIC in power off

	scenarios. So for GPIO7 if ti,palmas-override-powerhold is set

	then the GPIO_7 field should never be muxed to anything else.

	It should be set to POWERHOLD by default and only in case of

	power off scenarios the driver will over ride the mux value.

This binding uses the following generic properties as defined in

pinctrl-bindings.txt:

offprjjquota           Turn off project journelled quota.

quota                  Enable plain user disk quota accounting.

noquota                Disable all plain disk quota option.

whint_mode=%s          Control which write hints are passed down to block

                       layer. This supports "off", "user-based", and

                       "fs-based".  In "off" mode (default), f2fs does not pass

                       down hints. In "user-based" mode, f2fs tries to pass

                       down hints given by users. And in "fs-based" mode, f2fs

                       passes down hints with its policy.

alloc_mode=%s          Adjust block allocation policy, which supports "reuse"

                       and "default".

fsync_mode=%s          Control the policy of fsync. Currently supports "posix"

                       and "strict". In "posix" mode, which is default, fsync

                       will follow POSIX semantics and does a light operation

                       to improve the filesystem performance. In "strict" mode,

                       fsync will be heavy and behaves in line with xfs, ext4

                       and btrfs, where xfstest generic/342 will pass, but the

                       performance will regress.

test_dummy_encryption  Enable dummy encryption, which provides a fake fscrypt

                       context. The fake fscrypt context is used by xfstests.

================================================================================

DEBUGFS ENTRIES

a7cb1000-a7cb2000 ---p 00000000 00:00 0

a7cb2000-a7eb2000 rw-p 00000000 00:00 0

a7eb2000-a7eb3000 ---p 00000000 00:00 0

a7eb3000-a7ed5000 rw-p 00000000 00:00 0          [stack:1001]

a7eb3000-a7ed5000 rw-p 00000000 00:00 0

a7ed5000-a8008000 r-xp 00000000 03:00 4222       /lib/libc.so.6

a8008000-a800a000 r--p 00133000 03:00 4222       /lib/libc.so.6

a800a000-a800b000 rw-p 00135000 03:00 4222       /lib/libc.so.6

 [heap]                   = the heap of the program

 [stack]                  = the stack of the main process

 [stack:1001]             = the stack of the thread with tid 1001

 [vdso]                   = the "virtual dynamic shared object",

                            the kernel system call handler

 [anon:<name>]            = an anonymous mapping that has been

 or if empty, the mapping is anonymous.

The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint

of the individual tasks of a process. In this file you will see a mapping marked

as [stack] if that task sees it as a stack. This is a key difference from the

content of /proc/PID/maps, where you will see all mappings that are being used

as stack by all of those tasks. Hence, for the example above, the task-level

map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:

08048000-08049000 r-xp 00000000 03:00 8312       /opt/test

08049000-0804a000 rw-p 00001000 03:00 8312       /opt/test

0804a000-0806b000 rw-p 00000000 00:00 0          [heap]

a7cb1000-a7cb2000 ---p 00000000 00:00 0

a7cb2000-a7eb2000 rw-p 00000000 00:00 0

a7eb2000-a7eb3000 ---p 00000000 00:00 0

a7eb3000-a7ed5000 rw-p 00000000 00:00 0          [stack]

a7ed5000-a8008000 r-xp 00000000 03:00 4222       /lib/libc.so.6

a8008000-a800a000 r--p 00133000 03:00 4222       /lib/libc.so.6

a800a000-a800b000 rw-p 00135000 03:00 4222       /lib/libc.so.6

a800b000-a800e000 rw-p 00000000 00:00 0

a800e000-a8022000 r-xp 00000000 03:00 14462      /lib/libpthread.so.0

a8022000-a8023000 r--p 00013000 03:00 14462      /lib/libpthread.so.0

a8023000-a8024000 rw-p 00014000 03:00 14462      /lib/libpthread.so.0

a8024000-a8027000 rw-p 00000000 00:00 0

a8027000-a8043000 r-xp 00000000 03:00 8317       /lib/ld-linux.so.2

a8043000-a8044000 r--p 0001b000 03:00 8317       /lib/ld-linux.so.2

a8044000-a8045000 rw-p 0001c000 03:00 8317       /lib/ld-linux.so.2

aff35000-aff4a000 rw-p 00000000 00:00 0

ffffe000-fffff000 r-xp 00000000 00:00 0          [vdso]

The /proc/PID/smaps is an extension based on maps, showing the memory

consumption for each of the process's mappings. For each of mappings there

is a series of lines such as the following:

VERSION = 3

PATCHLEVEL = 18

SUBLEVEL = 102

SUBLEVEL = 105

EXTRAVERSION =

NAME = Diseased Newt