From: David Laight <david.laight.linux@gmail.com>
To: Lance Yang <ioworker0@gmail.com>
Cc: baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, axelrasmussen@google.com,
chandna.sahil@gmail.com, chengming.zhou@linux.dev,
david@kernel.org, david@redhat.com, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, mhocko@suse.com, nphamcs@gmail.com,
rppt@kernel.org, shakeel.butt@linux.dev, surenb@google.com,
vbabka@suse.cz, weixugc@google.com, willy@infradead.org,
yosry.ahmed@linux.dev, yuanchu@google.com,
zhengqi.arch@bytedance.com, Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH v4 1/3] mm: pagewalk: simplify hugepage boundary
Date: Wed, 24 Dec 2025 14:08:29 +0000 [thread overview]
Message-ID: <20251224140829.2ec7bbae@pumpkin> (raw)
In-Reply-To: <20251224092332.53214-1-ioworker0@gmail.com>
On Wed, 24 Dec 2025 17:23:32 +0800
Lance Yang <ioworker0@gmail.com> wrote:
> From: Lance Yang <lance.yang@linux.dev>
>
>
> On Wed, 24 Dec 2025 15:50:34 +0800, Baolin Wang wrote:
> > Hi Andrew,
> >
> > On 2025/11/28 15:01, Sahil Chandna wrote:
> > > Replace hugepage boundary computation with ALIGN() helper instead of
> > > an open coded expression. This helps to improves code readability.
> > >
> > > This was flagged by Coccinelle (misc/minmax.cocci) as an opportunity
> > > to use min(), after which the boundary computation was updated following
> > > review suggestions.
> > >
> > > Found by: make coccicheck MODE=report M=mm/
> > > No functional change intended.
> > >
> > > Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
> > > Suggested-by: David Hildenbrand (Red Hat) <david@kernel.org>
> > > Suggested-by: Matthew Wilcox <willy@infradead.org>
> > > Suggested-by: David Laight <david.laight.linux@gmail.com>
> > > Signed-off-by: Sahil Chandna <chandna.sahil@gmail.com>
> > > ---
> > > mm/pagewalk.c | 3 +--
> > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/mm/pagewalk.c b/mm/pagewalk.c
> > > index 9f91cf85a5be..9fd59d517f37 100644
> > > --- a/mm/pagewalk.c
> > > +++ 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().)
David
>
> >
> > This patch does introduce functional changes and makes an incorrect
> > assumption that the 'end' must be aligned to the hugepage size. However,
>
> Yep. This patch is not equivalent to the original code when addr is
> already aligned :)
>
> > this is not necessarily the case. For example, see how pagemap_read()
> > calculates the 'end':
> >
> > "
> > end = start_vaddr + ((count / PM_ENTRY_BYTES) << PAGE_SHIFT);
> > "
> >
> > Revert this patch, mm selftests work well.
next prev parent reply other threads:[~2025-12-24 14:08 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 [this message]
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
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=20251224140829.2ec7bbae@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=chandna.sahil@gmail.com \
--cc=chengming.zhou@linux.dev \
--cc=david@kernel.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=ioworker0@gmail.com \
--cc=lance.yang@linux.dev \
--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.