+ vmcoreinfo-export-section_has_mem_map.patch added to mm-unstable branch

+ vmcoreinfo-export-section_has_mem_map.patch added to mm-unstable branch

[Andrew Morton]

The patch titled
     Subject: vmcoreinfo: export SECTION_HAS_MEM_MAP
has been added to the -mm mm-unstable branch.  Its filename is
     vmcoreinfo-export-section_has_mem_map.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/vmcoreinfo-export-section_has_mem_map.patch

This patch will later appear in the mm-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days

------------------------------------------------------
From: "David Hildenbrand (Arm)" <david@kernel.org>
Subject: vmcoreinfo: export SECTION_HAS_MEM_MAP
Date: Mon, 28 Sep 2026 10:48:21 +0200

The crash tool currently hardcodes SECTION_HAS_MEM_MAP, and makedumpfile
needs similar information (although still relying on
SECTION_MARKED_PRESENT, it should switch to SECTION_HAS_MEM_MAP).

Let's just export the value instead, so tools that work on vmcoreinfo
will not have to guess.

Link: https://lore.kernel.org/20260928-section_has_mem_map-v1-1-4129f6ba2838@kernel.org
Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Baoquan He <baoquan.he@linux.dev>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: David Carlier <devnexen@gmail.com>
Cc: Dave Young <ruirui.yang@linux.dev>
Cc: Kazuhito Hagio <kazuhito.hagio@nec.com>
---

 kernel/vmcore_info.c |    1 +
 1 file changed, 1 insertion(+)

--- a/kernel/vmcore_info.c~vmcoreinfo-export-section_has_mem_map
+++ a/kernel/vmcore_info.c
@@ -182,6 +182,7 @@ static int __init crash_save_vmcoreinfo_
 	VMCOREINFO_STRUCT_SIZE(mem_section);
 	VMCOREINFO_OFFSET(mem_section, section_mem_map);
 	VMCOREINFO_NUMBER(SECTION_SIZE_BITS);
+	VMCOREINFO_NUMBER(SECTION_HAS_MEM_MAP);
 	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
 #endif
 	VMCOREINFO_STRUCT_SIZE(page);
_

Patches currently in -mm which might be from david@kernel.org are

arm64-mm-move-__check_safe_pte_update-fix.patch
mm-sparse-move-mem_section-init-to-sparse_extreme_init.patch
mm-sparse-refactor-sparse_sections_init.patch
mm-sparse-move-initialization-of-section-metadata-to-sparse_metadata_init.patch
mm-sparse-rename-and-cleanup-sparse_init_nid.patch
mm-sparse-cleanup-sparse_init_one_section.patch
mm-sparse-rename-__highest_present_section_nr-to-__highest_used_section_nr.patch
mm-sparse-remove-pfn_in_present_section.patch
mm-sparse-move-__highest_used_section_nr-handling.patch
scripts-gdb-mmpy-remove-fallbacks-for-section_has_mem_map-and-section_is_early.patch
mm-sparse-remove-section_marked_present.patch
mm-sparse-remove-flags-parameter-from-sparse_init_one_section.patch
fs-proc-page-clarify-comment-in-get_max_dump_pfn.patch
mm-memory_hotplug-drop-config_have_arch_pfn_valid-handling-from-pfn_to_online_page.patch
vmcoreinfo-export-section_has_mem_map.patch

Re: + vmcoreinfo-export-section_has_mem_map.patch added to mm-unstable branch

[Bradley Morgan]

On 13 October 2026 16:26:40 BST, Andrew Morton <akpm@linux-foundation.org>
wrote:
>
>The patch titled
>     Subject: vmcoreinfo: export SECTION_HAS_MEM_MAP
>has been added to the -mm mm-unstable branch.  Its filename is
>     vmcoreinfo-export-section_has_mem_map.patch
>
>This patch will shortly appear at
>     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/vmcoreinfo-export-section_has_mem_map.patch
>
>This patch will later appear in the mm-unstable branch at
>    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
>Before you just go and hit "reply", please:
>   a) Consider who else should be cc'ed
>   b) Prefer to cc a suitable mailing list as well
>   c) Ideally: find the original patch on the mailing list and do a
>      reply-to-all to that, adding suitable additional cc's
>
>*** Remember to use Documentation/process/submit-checklist.rst when
>testing your code ***
>
>The -mm tree is included into linux-next via various
>branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>and is updated there most days
>
>------------------------------------------------------
>From: "David Hildenbrand (Arm)" <david@kernel.org>
>Subject: vmcoreinfo: export SECTION_HAS_MEM_MAP
>Date: Mon, 28 Sep 2026 10:48:21 +0200
>
>The crash tool currently hardcodes SECTION_HAS_MEM_MAP, and makedumpfile
>needs similar information (although still relying on
>SECTION_MARKED_PRESENT, it should switch to SECTION_HAS_MEM_MAP).
>
>Let's just export the value instead, so tools that work on vmcoreinfo
>will not have to guess.
>
>Link: https://lore.kernel.org/20260928-section_has_mem_map-v1-1-4129f6ba2838@kernel.org
>Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>Acked-by: Baoquan He <baoquan.he@linux.dev>
>Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>

Sigh... :(

https://lore.kernel.org/all/E7FBE134-976C-4FAE-A25F-52225118557F@mainlining.org/


>Cc: David Carlier <devnexen@gmail.com>
>Cc: Dave Young <ruirui.yang@linux.dev>
>Cc: Kazuhito Hagio <kazuhito.hagio@nec.com>
>---
>
> kernel/vmcore_info.c |    1 +
> 1 file changed, 1 insertion(+)
>
>--- a/kernel/vmcore_info.c~vmcoreinfo-export-section_has_mem_map
>+++ a/kernel/vmcore_info.c
>@@ -182,6 +182,7 @@ static int __init crash_save_vmcoreinfo_
> 	VMCOREINFO_STRUCT_SIZE(mem_section);
> 	VMCOREINFO_OFFSET(mem_section, section_mem_map);
> 	VMCOREINFO_NUMBER(SECTION_SIZE_BITS);
>+	VMCOREINFO_NUMBER(SECTION_HAS_MEM_MAP);
> 	VMCOREINFO_NUMBER(MAX_PHYSMEM_BITS);
> #endif
> 	VMCOREINFO_STRUCT_SIZE(page);
>_
>
>Patches currently in -mm which might be from david@kernel.org are
>
>arm64-mm-move-__check_safe_pte_update-fix.patch
>mm-sparse-move-mem_section-init-to-sparse_extreme_init.patch
>mm-sparse-refactor-sparse_sections_init.patch
>mm-sparse-move-initialization-of-section-metadata-to-sparse_metadata_init.patch
>mm-sparse-rename-and-cleanup-sparse_init_nid.patch
>mm-sparse-cleanup-sparse_init_one_section.patch
>mm-sparse-rename-__highest_present_section_nr-to-__highest_used_section_nr.patch
>mm-sparse-remove-pfn_in_present_section.patch
>mm-sparse-move-__highest_used_section_nr-handling.patch
>scripts-gdb-mmpy-remove-fallbacks-for-section_has_mem_map-and-section_is_early.patch
>mm-sparse-remove-section_marked_present.patch
>mm-sparse-remove-flags-parameter-from-sparse_init_one_section.patch
>fs-proc-page-clarify-comment-in-get_max_dump_pfn.patch
>mm-memory_hotplug-drop-config_have_arch_pfn_valid-handling-from-pfn_to_online_page.patch
>vmcoreinfo-export-section_has_mem_map.patch
>
>
>

--- Thanks!
"I'm not a very positive person" - Linus torvalds