From: sashiko-bot@kernel.org
To: "Artem Dinaburg" <artem@trailofbits.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 6.6.y 1/2] jbd2: check need_resched() when skipping busy checkpoint buffers
Date: Thu, 08 Oct 2026 19:26:06 +0000 [thread overview]
Message-ID: <sashiko-outbox-164517@kernel.org> (raw)
In-Reply-To: <20261008192048.98833-2-artem@trailofbits.com>
> From: Max Kellermann <max.kellermann@ionos.com>
>
> [ Upstream commit f213e12ff5c9590b1034ae8da0e6d09665c772d0 ]
>
> journal_shrink_one_cp_list() skips busy checkpoint buffers when called
> with JBD2_SHRINK_BUSY_SKIP. The continue statement on this path also
> skips the need_resched() check at the end of the loop body.
>
> Consequently, when a checkpoint list contains mostly busy buffers, the
> shrinker can walk the entire list while holding journal->j_list_lock,
> even when a reschedule has been requested. Large checkpoint lists under
> memory pressure can therefore cause long lock hold times and leave other
> CPUs spinning on j_list_lock, resulting in soft lockups or RCU stalls.
>
> Route the busy-buffer path through the need_resched() check so that the
> [ ... ]
> Reviewed-by: Jan Kara <jack@suse.cz>
> Link: https://patch.msgid.link/20260713102229.1598812-2-max.kellermann@ionos.com
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Assisted-by: LLM
> Signed-off-by: Artem Dinaburg <artem@trailofbits.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008192048.98833-1-artem@trailofbits.com?part=1
next prev parent reply other threads:[~2026-10-08 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 19:20 [PATCH 6.6.y 0/2] jbd2: backport CVE-2026-89566, CVE-2026-89567 Artem Dinaburg
2026-10-08 19:20 ` [PATCH 6.6.y 1/2] jbd2: check need_resched() when skipping busy checkpoint buffers Artem Dinaburg
2026-10-08 19:26 ` sashiko-bot [this message]
2026-10-08 19:20 ` [PATCH 6.6.y 2/2] jbd2: bound shrinker scans by examined " Artem Dinaburg
2026-10-08 19:29 ` sashiko-bot
2026-10-09 17:09 ` [PATCH 6.6.y 0/2] jbd2: backport CVE-2026-89566, CVE-2026-89567 Sasha Levin
2026-10-09 18:29 ` Theodore Tso
2026-10-10 22:12 ` Artem Dinaburg
2026-10-10 23:53 ` Theodore Tso
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=sashiko-outbox-164517@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=artem@trailofbits.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
/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.