From: Sahil Chandna <chandna.sahil@gmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
lorenzo.stoakes@oracle.com, mhocko@suse.com, vbabka@suse.cz,
rppt@kernel.org, surenb@google.com, hannes@cmpxchg.org,
shakeel.butt@linux.dev, zhengqi.arch@bytedance.com,
Liam.Howlett@oracle.com, weixugc@google.com,
axelrasmussen@google.com, yuanchu@google.com,
yosry.ahmed@linux.dev, nphamcs@gmail.com,
chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, david@kernel.org,
Sahil Chandna <chandna.sahil@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH v4 1/3] mm: pagewalk: simplify hugepage boundary
Date: Fri, 30 Jan 2026 16:04:10 +0530 [thread overview]
Message-ID: <aXyJInpe7WmGaEmP@chandna.localdomain> (raw)
In-Reply-To: <20251225100106.53e03519@pumpkin>
On Thu, Dec 25, 2025 at 10:01:06AM +0000, David Laight wrote:
>On Thu, 25 Dec 2025 10:32:46 +0100
>"David Hildenbrand (Red Hat)" <david@kernel.org> wrote:
>
>> On 12/24/25 19:06, Matthew Wilcox wrote:
>> > On Wed, Dec 24, 2025 at 02:08:29PM +0000, David Laight wrote:
>> >>>>> +++ b/mm/pagewalk.c
>> >>>>> @@ -312,8 +312,7 @@ static int walk_pgd_range(unsigned long addr, unsigned long end,
>> >>>>> static unsigned long hugetlb_entry_end(struct hstate *h, unsigned long addr,
>> >>>>> unsigned long end)
>> >>>>> {
>> >>>>> - unsigned long boundary = (addr & huge_page_mask(h)) + huge_page_size(h);
>> >>>>> - return boundary < end ? boundary : end;
>> >>>>> + return min(ALIGN(addr, huge_page_size(h)), end);
>> >>>>> }
>> >>>>
>> >>>> Please drop this patch from the mm-new branch, as it causes
>> >>>> 'run_vmtests.sh' to hang. Specifically, it leads to the system hanging
>> >>>> when executing hugepage-vmemmap test, because the program falls into an
>> >>>> infinite loop in walk_hugetlb_range() and cannot break out.
>> >>>
>> >>> Good catch! The problem is that ALIGN() returns addr itself when already
>> >>> aligned, causing the infinite loop ...
>> >>
>> >> Using ALIGN(addr + 1, huge_page_size(h)) would work.
>> >> Although it could be (addr + 1) & ~huge_page_mask(h) which is probably
>> >> the easiest to understand.
>> >> Some of the 'helper' macros don't really make the code easier to read.
>> >> (And that includes a lot of uses of min().)
>> >
>> > Or we could go back to my original suggestion.
>> >
>> > https://lore.kernel.org/linux-mm/aRyOWrARRlUCeEz6@casper.infradead.org/
>> >
>> > which was in v2:
>> >
>> > https://lore.kernel.org/linux-mm/f802959f58865371ba1b10081bced98e3784c5e4.1763796152.git.chandna.sahil@gmail.com/
>>
>> I'm starting to wonder whether we should just leave that code alone :)
>>
>
>Maybe 'we' should stop checkpatch (etc) suggesting min() in trivial
>cases. It doesn't really make the code better.
>
> David
Thank you for feedback, I dropped this patch this has been resubmitted [1].
This next two patches in this series were also dropped due to error in this
patch. Requesting feedback, if I can re-submit the other 2 patches which use
the "%pe" printk format specifier ?
Sharing reference to patches [2] and [3] below.
Thanks,
Sahil
[1] https://lore.kernel.org/all/39f4490a-d713-44a8-a1d7-3568b01b3dc2@kernel.org/
[2] https://lore.kernel.org/all/2c842a64fddeb0fe0cac087783aaedd97edc3191.1764312627.git.chandna.sahil@gmail.com/
[3] https://lore.kernel.org/all/6d729a60eb71baade3670e5bb609a068683af3eb.1764312627.git.chandna.sahil@gmail.com/
next prev parent reply other threads:[~2026-01-30 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 7:01 [PATCH v4 0/3] mm: Coccinelle-driven cleanups across memory management code Sahil Chandna
2025-11-28 7:01 ` [PATCH v4 1/3] mm: pagewalk: simplify hugepage boundary calculation Sahil Chandna
2025-12-24 7:50 ` Baolin Wang
2025-12-24 9:23 ` [PATCH v4 1/3] mm: pagewalk: simplify hugepage boundary Lance Yang
2025-12-24 12:46 ` Sahil Chandna
2025-12-24 14:08 ` David Laight
2025-12-24 18:06 ` Matthew Wilcox
2025-12-25 9:32 ` David Hildenbrand (Red Hat)
2025-12-25 10:01 ` David Laight
2026-01-30 10:34 ` Sahil Chandna [this message]
2025-11-28 7:01 ` [PATCH v4 2/3] mm/vmscan: use %pe to print error pointers Sahil Chandna
2025-11-28 7:01 ` [PATCH v4 3/3] mm/zswap: " Sahil Chandna
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=aXyJInpe7WmGaEmP@chandna.localdomain \
--to=chandna.sahil@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chengming.zhou@linux.dev \
--cc=david.laight.linux@gmail.com \
--cc=david@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yosry.ahmed@linux.dev \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.