From: Tianyi Chen <hi@tychen.cc>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] memblock tests: fix BUILD=32 address conversions
Date: Thu, 17 Sep 2026 00:11:03 +0800 [thread overview]
Message-ID: <20260916161105.2548281-1-hi@tychen.cc> (raw)
Fix two BUILD=32 failures: truncating a physical address before freeing
it, and sign-extending simulated memory addresses. Existing assertions
cover both regressions.
The runner passes with GCC in both allocation directions across 32-bit
builds, 32-bit phys_addr_t, and NUMA configurations. BUILD=32 NUMA=1 also
passes with Clang.
Tianyi Chen (2):
memblock tests: use physical free for the maximum-address check
memblock tests: zero-extend simulated memory addresses
tools/testing/memblock/tests/basic_api.c | 6 +++---
tools/testing/memblock/tests/common.c | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
base-commit: 5728d3523f12826a2b180c1c5738f74e33197e14
--
2.55.0
next reply other threads:[~2026-09-16 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:11 Tianyi Chen [this message]
2026-09-16 16:11 ` [PATCH 1/2] memblock tests: use physical free for the maximum-address check Tianyi Chen
2026-09-16 16:11 ` [PATCH 2/2] memblock tests: zero-extend simulated memory addresses Tianyi Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260916161105.2548281-1-hi@tychen.cc \
--to=hi@tychen.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®