Merge pull request #99 from microsoft/revert-98-hcl-main.6.12

Revert " Merge tag 'rolling-lts/hcl-main/6.12.42.1' into product/hcl-main/6.12"

Author: namancse

.clippy.toml

@@ -1,7 +1,5 @@
 # SPDX-License-Identifier: GPL-2.0
 
-msrv = "1.78.0"
-
 check-private-items = true
 
 disallowed-macros = [

Documentation/ABI/testing/sysfs-devices-system-cpu

@@ -523,7 +523,6 @@ What:		/sys/devices/system/cpu/vulnerabilities
 		/sys/devices/system/cpu/vulnerabilities/spectre_v1
 		/sys/devices/system/cpu/vulnerabilities/spectre_v2
 		/sys/devices/system/cpu/vulnerabilities/srbds
-		/sys/devices/system/cpu/vulnerabilities/tsa
 		/sys/devices/system/cpu/vulnerabilities/tsx_async_abort
 Date:		January 2018
 Contact:	Linux kernel mailing list <[email protected]>

Documentation/ABI/testing/sysfs-driver-ufs

@@ -711,7 +711,7 @@ Description:	This file shows the thin provisioning type. This is one of
 
 		The file is read only.
 
-What:		/sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resource_count
+What:		/sys/class/scsi_device/*/device/unit_descriptor/physical_memory_resourse_count
 Date:		February 2018
 Contact:	Stanislav Nijnikov <[email protected]>
 Description:	This file shows the total physical memory resources. This is

Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst

@@ -157,7 +157,9 @@ This is achieved by using the otherwise unused and obsolete VERW instruction in
 combination with a microcode update. The microcode clears the affected CPU
 buffers when the VERW instruction is executed.
 
-Kernel does the buffer clearing with x86_clear_cpu_buffers().
+Kernel reuses the MDS function to invoke the buffer clearing:
+
+	mds_clear_cpu_buffers()
 
 On MDS affected CPUs, the kernel already invokes CPU buffer clear on
 kernel/userspace, hypervisor/guest and C-state (idle) transitions. No

Documentation/admin-guide/kernel-parameters.txt

@@ -6997,19 +6997,6 @@
 			having this key zero'ed is acceptable. E.g. in testing
 			scenarios.
 
-	tsa=		[X86] Control mitigation for Transient Scheduler
-			Attacks on AMD CPUs. Search the following in your
-			favourite search engine for more details:
-
-			"Technical guidance for mitigating transient scheduler
-			attacks".
-
-			off		- disable the mitigation
-			on		- enable the mitigation (default)
-			user		- mitigate only user/kernel transitions
-			vm		- mitigate only guest/host transitions
-
-
 	tsc=		Disable clocksource stability checks for TSC.
 			Format: <string>
 			[x86] reliable: mark tsc clocksource as reliable, this

Documentation/arch/x86/mds.rst

@@ -93,7 +93,7 @@ enters a C-state.
 
 The kernel provides a function to invoke the buffer clearing:
 
-    x86_clear_cpu_buffers()
+    mds_clear_cpu_buffers()
 
 Also macro CLEAR_CPU_BUFFERS can be used in ASM late in exit-to-user path.
 Other than CFLAGS.ZF, this macro doesn't clobber any registers.
@@ -185,9 +185,9 @@ Mitigation points
    idle clearing would be a window dressing exercise and is therefore not
    activated.
 
-   The invocation is controlled by the static key cpu_buf_idle_clear which is
-   switched depending on the chosen mitigation mode and the SMT state of the
-   system.
+   The invocation is controlled by the static key mds_idle_clear which is
+   switched depending on the chosen mitigation mode and the SMT state of
+   the system.
 
    The buffer clear is only invoked before entering the C-State to prevent
    that stale data from the idling CPU from spilling to the Hyper-Thread

Documentation/bpf/map_hash.rst

@@ -233,16 +233,10 @@ attempts in order to enforce the LRU property which have increasing impacts on
 other CPUs involved in the following operation attempts:
 
 - Attempt to use CPU-local state to batch operations
-- Attempt to fetch ``target_free`` free nodes from global lists
+- Attempt to fetch free nodes from global lists
 - Attempt to pull any node from a global list and remove it from the hashmap
 - Attempt to pull any node from any CPU's list and remove it from the hashmap
 
-The number of nodes to borrow from the global list in a batch, ``target_free``,
-depends on the size of the map. Larger batch size reduces lock contention, but
-may also exhaust the global structure. The value is computed at map init to
-avoid exhaustion, by limiting aggregate reservation by all CPUs to half the map
-size. With a minimum of a single element and maximum budget of 128 at a time.
-
 This algorithm is described visually in the following diagram. See the
 description in commit 3a08c2fd7634 ("bpf: LRU List") for a full explanation of
 the corresponding operations:

Documentation/bpf/map_lru_hash_update.dot

@@ -35,18 +35,18 @@ digraph {
   fn_bpf_lru_list_pop_free_to_local [shape=rectangle,fillcolor=2,
     label="Flush local pending,
     Rotate Global list, move
-    target_free
+    LOCAL_FREE_TARGET
     from global -> local"]
   // Also corresponds to:
   // fn__local_list_flush()
   // fn_bpf_lru_list_rotate()
   fn___bpf_lru_node_move_to_free[shape=diamond,fillcolor=2,
-    label="Able to free\ntarget_free\nnodes?"]
+    label="Able to free\nLOCAL_FREE_TARGET\nnodes?"]
 
   fn___bpf_lru_list_shrink_inactive [shape=rectangle,fillcolor=3,
     label="Shrink inactive list
       up to remaining
-      target_free
+      LOCAL_FREE_TARGET
       (global LRU -> local)"]
   fn___bpf_lru_list_shrink [shape=diamond,fillcolor=2,
     label="> 0 entries in\nlocal free list?"]

Documentation/core-api/symbol-namespaces.rst

@@ -28,9 +28,6 @@ kernel. As of today, modules that make use of symbols exported into namespaces,
 are required to import the namespace. Otherwise the kernel will, depending on
 its configuration, reject loading the module or warn about a missing import.
 
-Additionally, it is possible to put symbols into a module namespace, strictly
-limiting which modules are allowed to use these symbols.
-
 2. How to define Symbol Namespaces
 ==================================
 
@@ -87,22 +84,6 @@ unit as preprocessor statement. The above example would then read::
 within the corresponding compilation unit before any EXPORT_SYMBOL macro is
 used.
 
-2.3 Using the EXPORT_SYMBOL_GPL_FOR_MODULES() macro
-===================================================
-
-Symbols exported using this macro are put into a module namespace. This
-namespace cannot be imported.
-
-The macro takes a comma separated list of module names, allowing only those
-modules to access this symbol. Simple tail-globs are supported.
-
-For example:
-
-  EXPORT_SYMBOL_GPL_FOR_MODULES(preempt_notifier_inc, "kvm,kvm-*")
-
-will limit usage of this symbol to modules whoes name matches the given
-patterns.
-
 3. How to use Symbols exported in Namespaces
 ============================================
 
@@ -174,6 +155,3 @@ in-tree modules::
 You can also run nsdeps for external module builds. A typical usage is::
 
 	$ make -C <path_to_kernel_src> M=$PWD nsdeps
-
-Note: it will happily generate an import statement for the module namespace;
-which will not work and generates build and runtime failures.

Documentation/filesystems/f2fs.rst

@@ -235,9 +235,9 @@ usrjquota=<file>	 Appoint specified file and type during mount, so that quota
 grpjquota=<file>	 information can be properly updated during recovery flow,
 prjjquota=<file>	 <quota file>: must be in root directory;
 jqfmt=<quota type>	 <quota type>: [vfsold,vfsv0,vfsv1].
-usrjquota=		 Turn off user journalled quota.
-grpjquota=		 Turn off group journalled quota.
-prjjquota=		 Turn off project journalled quota.
+offusrjquota		 Turn off user journalled quota.
+offgrpjquota		 Turn off group journalled quota.
+offprjjquota		 Turn off project journalled quota.
 quota			 Enable plain user disk quota accounting.
 noquota			 Disable all plain disk quota option.
 alloc_mode=%s		 Adjust block allocation policy, which supports "reuse"