From: "Darrick J. Wong" <djwong@kernel.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: cem@kernel.org, hch@lst.de, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] xfs: restore nofs context unconditionally in xfs_trans_roll
Date: Thu, 30 Jul 2026 08:51:25 -0700 [thread overview]
Message-ID: <20260730155125.GE3556460@frogsfrogsfrogs> (raw)
In-Reply-To: <20260730093002.1034320-1-yun.zhou@windriver.com>
On Thu, Jul 30, 2026 at 05:30:02PM +0800, Yun Zhou wrote:
> When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
> is cleared but only restored in the success path. This leaves the
> error path without nofs protection, causing a circular lock dependency
> between xfs_nondir_ilock_class and fs_reclaim:
>
> CPU0 CPU1
> ---- ----
> lock(&xfs_nondir_ilock_class);
> lock(fs_reclaim);
> lock(&xfs_nondir_ilock_class);
> lock(fs_reclaim);
>
> Fix this by moving xfs_trans_set_context() before the error check so
> that nofs context is always restored on the new transaction.
>
> Reported-by: syzbot+59178abfeb0ea3f0ab20@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=59178abfeb0ea3f0ab20
> Fixes: a1ca658d649a ("xfs: fix incorrect context handling in xfs_trans_roll")
> Cc: stable@vger.kernel.org
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Yun Zhou <yun.zhou@windriver.com>
Looks good to me,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> v3:
> - Change back to v1
>
> v2:
> - Instead of moving xfs_trans_set_context() before the error check,
> transfer the nofs context in xfs_trans_dup() via a new
> memalloc_flags_move() helper, as suggested by Darrick.
> - Change t_pflags from unsigned long to unsigned int to match mm API.
>
> v1: https://lore.kernel.org/all/20260713035505.1635191-1-yun.zhou@windriver.com/T/
>
> fs/xfs/xfs_trans.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/fs/xfs/xfs_trans.c b/fs/xfs/xfs_trans.c
> index 7bfbd9f6f0df..1b36cf12d4e3 100644
> --- a/fs/xfs/xfs_trans.c
> +++ b/fs/xfs/xfs_trans.c
> @@ -1029,6 +1029,15 @@ xfs_trans_roll(
> * duplicate transaction that gets returned.
> */
> error = __xfs_trans_commit(tp, true);
> +
> + tp = *tpp;
> + /*
> + * __xfs_trans_commit cleared the NOFS flag by calling into
> + * xfs_trans_free. Set it again here before doing memory
> + * allocations.
> + */
> + xfs_trans_set_context(tp);
> +
> if (error)
> return error;
>
> @@ -1040,13 +1049,6 @@ xfs_trans_roll(
> * either nothing be locked across this call, or that anything that is
> * locked be logged in the prior and the next transactions.
> */
> - tp = *tpp;
> - /*
> - * __xfs_trans_commit cleared the NOFS flag by calling into
> - * xfs_trans_free. Set it again here before doing memory
> - * allocations.
> - */
> - xfs_trans_set_context(tp);
> error = xfs_log_regrant(tp->t_mountp, tp->t_ticket);
> if (error)
> return error;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-07-30 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 9:30 Yun Zhou
2026-07-30 11:24 ` Christoph Hellwig
2026-07-30 15:51 ` Darrick J. Wong [this message]
2026-08-10 11:55 ` Carlos Maiolino
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=20260730155125.GE3556460@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yun.zhou@windriver.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 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®