[DO NOT MERGE] fuse: freezing abort when use wait_event_killable{, _e…

.gitignore

@@ -132,3 +132,6 @@ all.config
 
 # Kdevelop4
 *.kdev4
+
+# fetched Android config fragments
+kernel/configs/android-*.cfg

Documentation/ABI/testing/configfs-stp-policy-p_sys-t

@@ -0,0 +1,41 @@
+What:		/config/stp-policy/<device>:p_sys-t.<policy>/<node>/uuid
+Date:		June 2018
+KernelVersion:	4.19
+Description:
+		UUID source identifier string, RW.
+		Default value is randomly generated at the mkdir <node> time.
+		Data coming from trace sources that use this <node> will be
+		tagged with this UUID in the MIPI SyS-T packet stream, to
+		allow the decoder to discern between different sources
+		within the same master/channel range, and identify the
+		higher level decoders that may be needed for each source.
+
+What:		/config/stp-policy/<device>:p_sys-t.<policy>/<node>/do_len
+Date:		June 2018
+KernelVersion:	4.19
+Description:
+		Include payload length in the MIPI SyS-T header, boolean.
+		If enabled, the SyS-T protocol encoder will include payload
+		length in each packet's metadata. This is normally redundant
+		if the underlying transport protocol supports marking message
+		boundaries (which STP does), so this is off by default.
+
+What:		/config/stp-policy/<device>:p_sys-t.<policy>/<node>/ts_interval
+Date:		June 2018
+KernelVersion:	4.19
+Description:
+		Time interval in milliseconds. Include a timestamp in the
+		MIPI SyS-T packet metadata, if this many milliseconds have
+		passed since the previous packet from this source. Zero is
+		the default and stands for "never send the timestamp".
+
+What:		/config/stp-policy/<device>:p_sys-t.<policy>/<node>/clocksync_interval
+Date:		June 2018
+KernelVersion:	4.19
+Description:
+		Time interval in milliseconds. Send a CLOCKSYNC packet if
+		this many milliseconds have passed since the previous
+		CLOCKSYNC packet from this source. Zero is the default and
+		stands for "never send the CLOCKSYNC". It makes sense to
+		use this option with sources that generate constant and/or
+		periodic data, like stm_heartbeat.

Documentation/ABI/testing/configfs-usb-gadget-dvctrace

@@ -0,0 +1,9 @@
+What:		/config/usb-gadget/<gadget>/functions/dvctrace.<name>/source_dev
+Date:		Mar 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) The name of the source device paired with this function
+		instance, if upon creation of the instance a source device
+		named <name> exists and is free, the source device will be
+		associated with the current instance, otherwise the first free
+		source device will be used.

Documentation/ABI/testing/sysfs-bus-dvctrace

@@ -0,0 +1,68 @@
+What:		/sys/bus/dvctrace
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	Groups the devices and drivers registered to
+		to dvc-trace bus.
+
+What:		/sys/bus/dvctrace/devices/<device>/status
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) The status of a dvc-trace source device with
+		respect to an USB function driver.
+		  Free - The device is free
+		  Reserved - The device is reserved by an USB
+			function but not in use.
+		  In use - The device is used by an USB function.
+
+What:		/sys/bus/dvctrace/devices/<device>/protocol
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) The protocol id of a dvc-trace source device,
+		this will used in function driver interface
+		descriptors (u8). According to USB debug class
+		specification the protocol id is vendor specific.
+
+What:		/sys/bus/dvctrace/devices/<device>/descriptors
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Hex-dump of the descriptors provided by the
+		source device.
+		eg. A debug class output connection descriptor
+		09 24 02 04 03 00 00 00 00
+		ll tt ss xx xx xx xx xx ii
+		 |  |  |                 +- iConnection string id.
+		 |  |  +- Descriptor sub-type DC_OUTPUT_CONNECTION
+		 |  +- Descriptor type (USB_DT_CS_INTERFACE)
+		 +- Descriptor length
+		Writing:
+		  - is not allowed while the device is Reserved or In Use.
+		  - will replace all the descriptors currently present.
+		  - will remove any strings previously provided.
+		  - should use the same format.
+		  - accepts multiple descriptors separated by space or '\n'.
+
+What:		/sys/bus/dvctrace/devices/<device>/strings
+Date:		May 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Currently set usb descriptor strings in
+		<descriptor_index>.<offset>: string format.
+		<descriptor_index>.<offset> identifies the location where
+		the string id is needed.
+		eg. Having the same debug class output connection descriptor,
+		as the first descriptor.
+		09 24 02 04 03 00 00 00 00
+		ll tt ss xx xx xx xx xx ii
+		                         +- iConnection string id.
+		0.8: My output connection - will identify the string associated
+		with this descriptor.
+		Writing:
+		  - is not allowed while the device is Reserved or In Use.
+		  - will replace all the strings currently present.
+		  - should use the same format.
+		  - accepts multiple strings separated by ";" or '\n'.
+		    eg. "0.4: first string; 1.4: second string"

Documentation/ABI/testing/sysfs-bus-dvctrace-devices-dvcith

@@ -0,0 +1,68 @@
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/msc
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) Symbolic link to the Intel Trace Hub MSC
+		(Memory Storage Controller) sub-device used to get tracing data.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_min_transfer
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Window transfer watermark, the driver will queue a
+		new transfer only if at least <mdd_min_transfer> bytes
+		of trace data is available. Since on every switch @48 bytes
+		of trace data is generated, this should not be set under this
+		threshold.
+		Default 2048
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_retry_timeout
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Read retry interval, If by the time the last usb transfer
+		is complete, there is no new data to be sent the driver will
+		sleep <mdd_retry_timeout> ms, before checking again.
+		Default: 2 ms
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_max_retry
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) the maximum retries to be bone before triggering a switch
+		and sending the currently available data regardless of the
+		available size.
+		Default: 150
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_proc_type
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Data process type, during DvC tracing the MSC is set up in
+		Multi Window mode (check Intel Trace Hub Developer's Manual for
+		details), This attribute specifies what the dvc-trace data stream
+		should contain.
+		Available values are:
+		  - 1 - Full blocks,
+		  - 2 - Trimmed blocks (Block header + STP data)
+		  - 3 - STP data only.
+		Default 3.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_transfer_type
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(RW) Data transfer type, This attribute specifies how the trace data
+		is queued in the USB requests.
+		Available values are:
+		  - 1 - Auto,
+		  - 2 - SG-List,
+		  - 3 - Linear buffer.
+		Default 1.
+
+What:		/sys/bus/dvctrace/devices/dvcith-<device>/mdd_stats
+Date:		Aug 2015
+KernelVersion:	4.0
+Contact:	Traian Schiau <traianx.schiau@intel.com>
+Description:	(R) Provides statistical information regarding the latest.
+		trace session. Available if (CONFIG_INTEL_TH_MSU_DVC_DEBUG).

Documentation/ABI/testing/sysfs-bus-mei

@@ -26,3 +26,31 @@ KernelVersion:	4.3
 Contact:	Tomas Winkler <tomas.winkler@intel.com>
 Description:	Stores mei client protocol version
 		Format: %d
+
+What:		/sys/bus/mei/devices/.../max_conn
+Date:		Sep 2018
+KernelVersion:	4.19
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:	Stores mei client maximum number of connections
+		Format: %d
+
+What:		/sys/bus/mei/devices/.../fixed
+Date:		Sep 2018
+KernelVersion:	4.19
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:	Stores mei client fixed address, if any
+		Format: %d
+
+What:		/sys/bus/mei/devices/.../vtag
+Date:		Sep 2018
+KernelVersion:	4.19
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:	Stores mei client vm tag support status
+		Format: %d
+
+What:		/sys/bus/mei/devices/.../max_len
+Date:		Sep 2018
+KernelVersion:	4.19
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:	Stores mei client maximum message length
+		Format: %d

Documentation/ABI/testing/sysfs-class-mei

@@ -65,3 +65,18 @@ Description:	Display the ME firmware version.
 		<platform>:<major>.<minor>.<milestone>.<build_no>.
 		There can be up to three such blocks for different
 		FW components.
+
+What:		/sys/class/mei/meiN/dev_state
+Date:		Sep 2019
+KernelVersion:	4.19
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:	Display the ME device state.
+
+		The device state can have following values:
+		INITIALIZING
+		INIT_CLIENTS
+		ENABLED
+		RESETTING
+		DISABLED
+		POWER_DOWN
+		POWER_UP

Documentation/ABI/testing/sysfs-class-rpmb

@@ -0,0 +1,57 @@
+What:		/sys/class/rpmb/
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The rpmb/ class sub-directory belongs to RPMB device class.
+
+		Few storage technologies such is EMMC, UFS, and NVMe support
+		Replay Protected Memory Block (RPMB) hardware partition with
+		common protocol and similar frame layout.
+		Such a partition provides authenticated and replay protected access,
+		hence suitable as a secure storage.
+
+What:		/sys/class/rpmb/rpmbN/
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN directory is created for
+		each RPMB registered device.
+
+What:		/sys/class/rpmb/rpmbN/type
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/type file contains device
+		underlying storage type technology: EMMC, UFS, NVMe.
+		In case of simulated device it will have :SIM suffix
+		i.e EMMC:SIM.
+
+What:		/sys/class/rpmb/rpmbN/id
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/id file contains unique device id
+		in a binary form as defined by underlying storage device.
+		In case of multiple RPMB devices a user can determine correct
+		device.
+		The content can be parsed according the storage device type.
+
+What:		/sys/class/rpmb/rpmbN/wr_cnt_max
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/wr_cnt_max file contains
+		number of blocks that can be reliable written in a single request.
+
+What:		/sys/class/rpmb/rpmbN/rd_cnt_max
+Date:		Jul 2018
+KernelVersion:	4.18
+Contact:	Tomas Winkler <tomas.winkler@intel.com>
+Description:
+		The /sys/class/rpmb/rpmbN/rd_cnt_max file contains
+		number of blocks that can be read in a single request.

Documentation/ABI/testing/sysfs-kernel-wakeup_reasons

@@ -0,0 +1,16 @@
+What:		/sys/kernel/wakeup_reasons/last_resume_reason
+Date:		February 2014
+Contact:	Ruchi Kandoi <kandoiruchi@google.com>
+Description:
+		The /sys/kernel/wakeup_reasons/last_resume_reason is
+		used to report wakeup reasons after system exited suspend.
+
+What:		/sys/kernel/wakeup_reasons/last_suspend_time
+Date:		March 2015
+Contact:	jinqian <jinqian@google.com>
+Description:
+		The /sys/kernel/wakeup_reasons/last_suspend_time is
+		used to report time spent in last suspend cycle. It contains
+		two numbers (in seconds) separated by space. First number is
+		the time spent in suspend and resume processes. Second number
+		is the time spent in sleep state.

Documentation/admin-guide/LSM/index.rst

@@ -17,11 +17,16 @@ MAC extensions, other extensions can be built using the LSM to provide
 specific changes to system operation when these tweaks are not available
 in the core functionality of Linux itself.
 
-Without a specific LSM built into the kernel, the default LSM will be the
-Linux capabilities system. Most LSMs choose to extend the capabilities
-system, building their checks on top of the defined capability hooks.
-For more details on capabilities, see ``capabilities(7)`` in the Linux
-man-pages project.
+The Linux capabilities modules will always be included. For more details
+on capabilities, see ``capabilities(7)`` in the Linux man-pages project.
+
+Security modules that do not use the security data blobs maintained
+by the LSM infrastructure are considered "minor" modules. These may be
+included at compile time and stacked explicitly. Security modules that
+use the LSM maintained security blobs are considered "major" modules.
+These may only be stacked if the CONFIG_LSM_STACKED configuration
+option is used. If this is chosen all of the security modules selected
+will be used.
 
 A list of the active security modules can be found by reading
 ``/sys/kernel/security/lsm``. This is a comma separated list, and
@@ -30,6 +35,14 @@ order in which checks are made. The capability module will always
 be first, followed by any "minor" modules (e.g. Yama) and then
 the one "major" module (e.g. SELinux) if there is one configured.
 
+Process attributes associated with "major" security modules should
+be accessed and maintained using the special files in ``/proc/.../attr``.
+A security module may maintain a module specific subdirectory there,
+named after the module. ``/proc/.../attr/smack`` is provided by the Smack
+security module and contains all its special files. The files directly
+in ``/proc/.../attr`` remain as legacy interfaces for modules that provide
+subdirectories.
+
 .. toctree::
    :maxdepth: 1
 

Documentation/admin-guide/kernel-parameters.txt

@@ -741,6 +741,10 @@
 			Format: <port#>,<type>
 			See also Documentation/input/devices/joystick-parport.rst
 
+	dev_sec_info.param_addr=
+			[BOOT] address of automotive bootloader (abl)
+			security parameters.
+
 	ddebug_query=	[KNL,DYNAMIC_DEBUG] Enable debug messages at early boot
 			time. See
 			Documentation/admin-guide/dynamic-debug-howto.rst for
@@ -880,6 +884,9 @@
 
 	dis_ucode_ldr	[X86] Disable the microcode loader.
 
+	dm=		[DM] Allows early creation of a device-mapper device.
+			See Documentation/device-mapper/boot.txt.
+
 	dma_debug=off	If the kernel is compiled with DMA_API_DEBUG support,
 			this option disables the debugging code at boot.
 
@@ -3899,6 +3906,9 @@
 			      reboot_cpu is s[mp]#### with #### being the processor
 					to be used for rebooting.
 
+	reboot_panic=	[KNL]
+			Same as reboot parameter above but only in case of panic.
+
 	relax_domain_level=
 			[KNL, SMP] Set scheduler's default relax_domain_level.
 			See Documentation/cgroup-v1/cpusets.txt.