Merge tag 'mm-stable-2022-08-09' of git://git.kernel.org/pub/scm/linux/kernel/git...

Pull remaining MM updates from Andrew Morton:
 "Three patch series - two that perform cleanups and one feature:

   - hugetlb_vmemmap cleanups from Muchun Song

   - hardware poisoning support for 1GB hugepages, from Naoya Horiguchi

   - highmem documentation fixups from Fabio De Francesco"

* tag 'mm-stable-2022-08-09' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (23 commits)
  Documentation/mm: add details about kmap_local_page() and preemption
  highmem: delete a sentence from kmap_local_page() kdocs
  Documentation/mm: rrefer kmap_local_page() and avoid kmap()
  Documentation/mm: avoid invalid use of addresses from kmap_local_page()
  Documentation/mm: don't kmap*() pages which can't come from HIGHMEM
  highmem: specify that kmap_local_page() is callable from interrupts
  highmem: remove unneeded spaces in kmap_local_page() kdocs
  mm, hwpoison: enable memory error handling on 1GB hugepage
  mm, hwpoison: skip raw hwpoison page in freeing 1GB hugepage
  mm, hwpoison: make __page_handle_poison returns int
  mm, hwpoison: set PG_hwpoison for busy hugetlb pages
  mm, hwpoison: make unpoison aware of raw error info in hwpoisoned hugepage
  mm, hwpoison, hugetlb: support saving mechanism of raw error pages
  mm/hugetlb: make pud_huge() and follow_huge_pud() aware of non-present pud entry
  mm/hugetlb: check gigantic_page_runtime_supported() in return_unused_surplus_pages()
  mm: hugetlb_vmemmap: use PTRS_PER_PTE instead of PMD_SIZE / PAGE_SIZE
  mm: hugetlb_vmemmap: move code comments to vmemmap_dedup.rst
  mm: hugetlb_vmemmap: improve hugetlb_vmemmap code readability
  mm: hugetlb_vmemmap: replace early_param() with core_param()
  mm: hugetlb_vmemmap: move vmemmap code related to HugeTLB to hugetlb_vmemmap.c
  ...

diff --combined Documentation/admin-guide/kernel-parameters.txt
index 54a9756f2dad610aef55b57a048c15ce9654566c,8c06271835b03da46e8d57ce665d03420e1e0af5..db5de5f0b9d3009b8b4a12cc1b5557c58a3ea325
--- 1/Documentation/admin-guide/kernel-parameters.txt
--- 2/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@@ -1158,12 -1158,8 +1158,12 @@@
        nopku           [X86] Disable Memory Protection Keys CPU feature found
                        in some Intel CPUs.
  
 -      <module>.async_probe [KNL]
 -                      Enable asynchronous probe on this module.
 +      <module>.async_probe[=<bool>] [KNL]
 +                      If no <bool> value is specified or if the value
 +                      specified is not a valid <bool>, enable asynchronous
 +                      probe on this module.  Otherwise, enable/disable
 +                      asynchronous probe on this module as indicated by the
 +                      <bool> value. See also: module.async_probe
  
        early_ioremap_debug [KNL]
                        Enable debug messages in early_ioremap support. This
@@@ -1735,12 -1731,13 +1735,13 @@@
        hugetlb_free_vmemmap=
                        [KNL] Reguires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
                        enabled.
+                       Control if HugeTLB Vmemmap Optimization (HVO) is enabled.
                        Allows heavy hugetlb users to free up some more
                        memory (7 * PAGE_SIZE for each 2MB hugetlb page).
-                       Format: { [oO][Nn]/Y/y/1 | [oO][Ff]/N/n/0 (default) }
+                       Format: { on | off (default) }
  
-                       [oO][Nn]/Y/y/1: enable the feature
-                       [oO][Ff]/N/n/0: disable the feature
+                       on: enable HVO
+                       off: disable HVO
  
                        Built with CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON=y,
                        the default is on.
@@@ -3281,15 -3278,6 +3282,15 @@@
                        For details see:
                        Documentation/admin-guide/hw-vuln/processor_mmio_stale_data.rst
  
 +      module.async_probe=<bool>
 +                      [KNL] When set to true, modules will use async probing
 +                      by default. To enable/disable async probing for a
 +                      specific module, use the module specific control that
 +                      is documented under <module>.async_probe. When both
 +                      module.async_probe and <module>.async_probe are
 +                      specified, <module>.async_probe takes precedence for
 +                      the specific module.
 +
        module.sig_enforce
                        [KNL] When CONFIG_MODULE_SIG is set, this means that
                        modules without (valid) signatures will fail to load.