From: "Darrick J. Wong" <djwong@kernel.org>
To: "Zhou, Yun" <yun.zhou@windriver.com>
Cc: Christoph Hellwig <hch@infradead.org>,
cem@kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] xfs: restore nofs context unconditionally in xfs_trans_roll
Date: Tue, 14 Jul 2026 10:55:28 -0700 [thread overview]
Message-ID: <20260714175528.GG7380@frogsfrogsfrogs> (raw)
In-Reply-To: <0792c175-6a7c-4108-966d-4afbc8c515a2@windriver.com>
[add linux-mm since we're talking about memalloc_nofs_save]
On Tue, Jul 14, 2026 at 10:15:53AM +0800, Zhou, Yun wrote:
>
>
> On 7/14/26 07:04, Darrick J. Wong wrote:
> > CAUTION: This email comes from a non Wind River email account!
> > Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >
> > On Mon, Jul 13, 2026 at 06:28:38AM -0700, Christoph Hellwig wrote:
> > > On Mon, Jul 13, 2026 at 06:06:38PM +0800, Zhou, Yun wrote:
> > > >
> > > >
> > > > On 7/13/26 17:09, Christoph Hellwig wrote:
> > > > >
> > > > > On Mon, Jul 13, 2026 at 11:55:05AM +0800, Yun Zhou wrote:
> > > > > >
> > > > > > 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);
> > > > >
> > > > > The tp assignment above now returns the incorrect transaction when
> > > > > __xfs_trans_commit fails, so you can't do this.
> > > > >
> > > > > Otherwise yes, this call should move up. I don't really see how
> > > > > it fixes the syzbot report, though.
> > > > >
> > > >
> > > > Thank you very much for your reply. The tp here is a local variable only
> > > > used for convenience within the function. The caller always gets the new
> > > > transaction through *tpp, which was set by xfs_trans_dup() before the commit
> > > > call. Moving tp = *tpp before the error check doesn't change what the caller
> > > > sees - *tpp still points to the new (dup'd) transaction regardless.
> > >
> > > Ah, right. Tis should be fine:
> > >
> > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> >
> > Why not move tp_pflags to the new transaction in xfs_trans_dup like we
> > do for the deferred item list:
> >
> > /* move deferred ops over to the new tp */
> > xfs_defer_move(ntp, tp);
> >
> > ntp->t_pflags = tp->t_pflags;
> > tp->t_pflags = 0;
> >
>
> That's what the old xfs_trans_switch_context() did before a1ca658d649a
> removed it. The problem is that setting tp->t_pflags = 0 means
> xfs_trans_free() calls memalloc_nofs_restore(0), which relies on that being
> a no-op — an mm implementation detail. A fresh memalloc_nofs_save() on the
> new tp keeps the save/restore pairing correct unconditionally.
So add a new helper.
/**
* memalloc_flags_take - move an implicit __GFP_MEMALLOC scope from one
* tracking structure to another.
*/
static inline unsigned int
memalloc_flags_take(unsigned int *old_flags)
{
unsigned int ret = *old_flags;
*old_flags = 0;
return ret;
}
and then:
/* move deferred ops over to the new tp */
xfs_defer_move(ntp, tp);
ntp->t_pflags = memalloc_flags_take(&tp->t_pflags);
--D
> BR,
> Yun
>
next parent reply other threads:[~2026-07-14 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260713035505.1635191-1-yun.zhou@windriver.com>
[not found] ` <alSrO3aDTuZkX0K9@infradead.org>
[not found] ` <7a053113-f678-486e-a78b-8f5e94e73acb@windriver.com>
[not found] ` <alToBmAN_HyeXth9@infradead.org>
[not found] ` <20260713230420.GN7195@frogsfrogsfrogs>
[not found] ` <0792c175-6a7c-4108-966d-4afbc8c515a2@windriver.com>
2026-07-14 17:55 ` Darrick J. Wong [this message]
2026-07-14 18:15 ` [PATCH] xfs: restore nofs context unconditionally in xfs_trans_roll Matthew Wilcox
2026-07-14 18:53 ` Darrick J. Wong
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=20260714175528.GG7380@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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