diff options
| author | Zhenhua Huang <[email protected]> | 2025-03-21 07:00:19 +0000 |
|---|---|---|
| committer | Catalin Marinas <[email protected]> | 2025-03-28 19:18:29 +0000 |
| commit | 89f43e1ce6f60d4f44399059595ac47f7a90a393 (patch) | |
| tree | 992944f392103ebf5d3d0238a8c000cfb9662929 /net/core/lock_debug.c | |
| parent | Merge branch 'for-next/el2-enable-feat-pmuv3p9' into for-next/core (diff) | |
| download | kernel-89f43e1ce6f60d4f44399059595ac47f7a90a393.tar.gz kernel-89f43e1ce6f60d4f44399059595ac47f7a90a393.zip | |
arm64: mm: Correct the update of max_pfn
Hotplugged memory can be smaller than the original memory. For example,
on my target:
root@genericarmv8:~# cat /sys/kernel/debug/memblock/memory
0: 0x0000000064005000..0x0000000064023fff 0 NOMAP
1: 0x0000000064400000..0x00000000647fffff 0 NOMAP
2: 0x0000000068000000..0x000000006fffffff 0 DRV_MNG
3: 0x0000000088800000..0x0000000094ffefff 0 NONE
4: 0x0000000094fff000..0x0000000094ffffff 0 NOMAP
max_pfn will affect read_page_owner. Therefore, it should first compare and
then select the larger value for max_pfn.
Fixes: 8fac67ca236b ("arm64: mm: update max_pfn after memory hotplug")
Cc: <[email protected]> # 6.1.x
Signed-off-by: Zhenhua Huang <[email protected]>
Acked-by: David Hildenbrand <[email protected]>
Reviewed-by: Anshuman Khandual <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Catalin Marinas <[email protected]>
Diffstat (limited to 'net/core/lock_debug.c')
0 files changed, 0 insertions, 0 deletions