From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Gregory Price <gourry@gourry.net>
Cc: albin_yang@163.com, akpm@linux-foundation.org,
liam@infradead.org, david@kernel.org, vbabka@kernel.org,
jannh@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, albinwyang@tencent.com
Subject: Re: [PATCH] mm/madvise: add cond_resched() in THP branch of madvise_cold_or_pageout_pte_range()
Date: Mon, 12 Oct 2026 13:58:18 +0100 [thread overview]
Message-ID: <aszZPq92qX3jpsNE@gremlin> (raw)
In-Reply-To: <aspKmWIrOzNjiP-t@gourry-fedora-PF4VCD3F>
On Sat, Oct 10, 2026 at 10:26:33AM -0400, Gregory Price wrote:
> On Sat, Oct 10, 2026 at 10:40:42AM +0800, albin_yang@163.com wrote:
> > From: Wei Yang <albinwyang@tencent.com>
> >
> > Crash log:
> > watchdog: BUG: soft lockup - CPU#63 stuck for 23s! [stress-ng-vm:1665914]
> > ...
> > Call trace:
> > pmdp_invalidate+0x48/0x68
> > madvise_cold_or_pageout_pte_range+0x84c/0xb00
> > walk_pmd_range.isra.0+0x1ac/0x3b0
> > walk_pud_range+0x120/0x190
> > walk_pgd_range+0x170/0x1b8
> > __walk_page_range+0x184/0x198
> > walk_page_range_vma+0x94/0x128
> > madvise_cold+0xd8/0x198
> > madvise_vma_behavior+0x234/0x638
> > madvise_walk_vmas.constprop.0+0xdc/0x210
> > madvise_do_behavior+0xa8/0x328
> > do_madvise+0xd8/0x140
> > __arm64_sys_madvise+0x2c/0xe0
> >
> > Signed-off-by: Wei Yang <albinwyang@tencent.com>
> > ---
> > mm/madvise.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/madvise.c b/mm/madvise.c
> > index eeee82cf2b3f..0755e6d99757 100644
> > --- a/mm/madvise.c
> > +++ b/mm/madvise.c
> > @@ -450,6 +450,7 @@ static int madvise_cold_or_pageout_pte_range(pmd_t *pmd,
> > spin_unlock(ptl);
> > if (pageout)
> > reclaim_pages(&folio_list);
> > + cond_resched();
> > return 0;
> > }
> >
>
> This same improvement came naturally from refactoring the entire
> function into a proper pagewalk structure:
>
> https://lore.kernel.org/linux-mm/20260922235830.2350770-10-gourry@gourry.net/
>
> this function is really nasty.
Nice!
And thank you for looking at this horror show of a function.
But yeah as Andrew said, need something for the backport, then your work can
help eliminate the source of such things! :)
>
> ~Gregory
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-12 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 2:40 albin_yang
2026-10-10 14:26 ` Gregory Price
2026-10-10 20:51 ` Andrew Morton
2026-10-12 12:58 ` Lorenzo Stoakes (ARM) [this message]
2026-10-12 13:32 ` Gregory Price
2026-10-12 13:49 ` Lorenzo Stoakes (ARM)
2026-10-12 11:02 ` David Hildenbrand (Arm)
2026-10-12 12:57 ` Lorenzo Stoakes (ARM)
2026-10-12 13:33 ` Gregory Price
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=aszZPq92qX3jpsNE@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=albin_yang@163.com \
--cc=albinwyang@tencent.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@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®