diff options
| author | Tianyi Chen <hi@tychen.cc> | 2026-09-23 11:31:23 +0900 |
|---|---|---|
| committer | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-24 10:56:52 +0300 |
| commit | 9357596afac61154e7f54048c0add9f1293b9eba (patch) | |
| tree | b0f03c2a108a2d9f7cb56bedf100b5fe246a15c4 /tools/lib/python/kdoc/parse_data_structs.py | |
| parent | 5728d3523f12826a2b180c1c5738f74e33197e14 (diff) | |
| download | linux-next-9357596afac61154e7f54048c0add9f1293b9eba.tar.gz linux-next-9357596afac61154e7f54048c0add9f1293b9eba.zip | |
memblock tests: use physical addresses for region removal
With BUILD=32, phys_addr_t remains 64-bit while pointers are 32-bit.
Casting the address near PHYS_ADDR_MAX to void * truncates it before
memblock_free() converts it back with __pa(). The reserved region is
therefore left unchanged and memblock_free_near_max_check() fails.
Use memblock_phys_free() for all synthetic physical ranges in the basic
API tests. This also removes the integer-to-pointer cast warnings from
the other removal checks. Retain the checks that freeing past
PHYS_ADDR_MAX clips the removed region.
Assisted-by: LLM
Signed-off-by: Tianyi Chen <hi@tychen.cc>
Link: https://patch.msgid.link/20260923023126.1910311-2-hi@tychen.cc
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/parse_data_structs.py')
0 files changed, 0 insertions, 0 deletions