From: Carlos Maiolino <cem@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: linux-xfs@vger.kernel.org, "Darrick J . Wong" <djwong@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH for-next v3] xfs: fix NOFS state corruption in btree split worker
Date: Mon, 21 Sep 2026 12:19:16 +0200 [thread overview]
Message-ID: <arEEdRBtMBxoPCEV@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260921071030.3214538-1-wangkefeng.wang@huawei.com>
On Mon, Sep 21, 2026 at 03:10:30PM +0800, Kefeng Wang wrote:
> xfs_btree_split_worker() calls xfs_trans_set_context() and
> xfs_trans_clear_context() on the caller's transaction, overwriting
> tp->t_pflags with the worker's NOFS state. When the caller already has
> PF_MEMALLOC_NOFS set (e.g. xfs_end_ioend_write, xfs_dio_write_end_io),
> the corrupted tp->t_pflags causes xfs_trans_free() to erroneously clear
> the caller's NOFS protection.
>
> Use memalloc_nofs_save/restore with a local variable instead so
> tp->t_pflags is never touched.
>
> Closes: https://sashiko.dev/#/patchset/20260902131653.1338227-1-wangkefeng.wang@huawei.com
> Fixes: 756b1c343333 ("xfs: use current->journal_info for detecting transaction recursion")
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Brian Foster <bfoster@redhat.com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Looks good,
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> v3:
> - Using correct unsigned int type for nofs_flags, per Darrick
>
> v2:
> - Send bugfix only based on xfs-linux/for-next, suggested by Carlos[1]
> https://lore.kernel.org/linux-xfs/aqqGiu9W0G7dquoY@nidhogg.toxiclabs.cc/
> v1:
> - https://lore.kernel.org/linux-xfs/20260911104227.2028941-1-wangkefeng.wang@huawei.com/
>
> fs/xfs/libxfs/xfs_btree.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_btree.c b/fs/xfs/libxfs/xfs_btree.c
> index 60ef7f08b1d3..239741132914 100644
> --- a/fs/xfs/libxfs/xfs_btree.c
> +++ b/fs/xfs/libxfs/xfs_btree.c
> @@ -3010,6 +3010,7 @@ xfs_btree_split_worker(
> struct xfs_btree_split_args, work);
> unsigned long pflags;
> unsigned long new_pflags = 0;
> + unsigned int nofs_flags;
>
> /*
> * we are in a transaction context here, but may also be doing work
> @@ -3021,12 +3022,17 @@ xfs_btree_split_worker(
> new_pflags |= PF_MEMALLOC | PF_KSWAPD;
>
> current_set_flags_nested(&pflags, new_pflags);
> - xfs_trans_set_context(args->cur->bc_tp);
> +
> + /*
> + * Don't use xfs_trans_set_context() here: it would overwrite the
> + * caller's saved NOFS state in tp->t_pflags. Use a local scope.
> + */
> + nofs_flags = memalloc_nofs_save();
>
> args->result = __xfs_btree_split(args->cur, args->level, args->ptrp,
> args->key, args->curp, args->stat);
>
> - xfs_trans_clear_context(args->cur->bc_tp);
> + memalloc_nofs_restore(nofs_flags);
> current_restore_flags_nested(&pflags, new_pflags);
>
> /*
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-09-21 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:10 [PATCH for-next v3] xfs: fix NOFS state corruption in btree split worker Kefeng Wang
2026-09-21 10:19 ` Carlos Maiolino [this message]
2026-09-21 14:22 ` Darrick J. Wong
2026-10-05 18:06 ` 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=arEEdRBtMBxoPCEV@nidhogg.toxiclabs.cc \
--to=cem@kernel.org \
--cc=bfoster@redhat.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=wangkefeng.wang@huawei.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