diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-24 10:52:42 +0300 |
|---|---|---|
| committer | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-24 10:57:13 +0300 |
| commit | 92248b75d0198f989a83187e683a774a9c608263 (patch) | |
| tree | fbc4fa01a7bd1338083c866e53106e4cd68494b5 /Documentation/admin-guide | |
| parent | 5728d3523f12826a2b180c1c5738f74e33197e14 (diff) | |
| parent | ba94f68b754985f77c3f6d3354df74952a1e0752 (diff) | |
| download | linux-next-92248b75d0198f989a83187e683a774a9c608263.tar.gz linux-next-92248b75d0198f989a83187e683a774a9c608263.zip | |
Merge patch series "memblock tests: fix BUILD=32 address conversions and warnings"
Tianyi Chen <hi@tychen.cc> says:
memblock tests: fix BUILD=32 address conversions and warnings
Fix the BUILD=32 physical-address truncation and sign-extension failures,
and address the remaining GCC warnings reported during review.
Validated with GCC 13.3.0 and Clang 18.1.3, retaining the default ASan
and UBSan flags and adding -Werror. Both compilers build without warnings
and pass ./main -v and ./main -m -v in each configuration:
- Default and NUMA=1.
- BUILD=32, with and without NUMA=1.
- 32BIT_PHYS_ADDR_T=1, with and without NUMA=1.
- BUILD=32 NUMA=1 MEMBLOCK_DEBUG=1.
Each run passes 189 checks without NUMA or 272 with NUMA, including both
allocation directions. A separate virt_to_phys() boundary check passes
with both compilers in 32- and 64-bit builds; GCC BUILD=32 failed it on
v1 for 0x80000000 due to sign extension.
* patches from https://patch.msgid.link/20260923023126.1910311-1-hi@tychen.cc
memblock tests: use physical addresses for region removal
memblock tests: zero-extend simulated memory addresses
tools: use __pa() in virt_to_phys()
memblock: initialize the region merge end index
Link: https://patch.msgid.link/20260923023126.1910311-1-hi@tychen.cc
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Diffstat (limited to 'Documentation/admin-guide')
0 files changed, 0 insertions, 0 deletions
