From: Christoph Hellwig <hch@infradead.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, akpm@linux-foundation.org
Subject: Re: [PATCH] xfs: fix nofs context corruption in xfs_btree_split_worker
Date: Fri, 24 Jul 2026 01:06:35 -0700 [thread overview]
Message-ID: <amMdC5fvYcsFXNmA@infradead.org> (raw)
In-Reply-To: <3f683dea-fdee-416a-8112-2db000c4cf4e@windriver.com>
On Fri, Jul 24, 2026 at 03:54:10PM +0800, Zhou, Yun wrote:
> Thanks a lot.
> I'd like to understand the scope you have in mind. Should the removal of
> xfs_trans_set/clear_context and current_set/restore_flags_nested be part of
> my nofs series, or is that something you'd prefer to handle separately?
I don't care too strongly. Maybe we should a minimal fix for the bug
in ASAP, and then we just need to agree who cleans up after that.
Happy to do that myself if you don't have the time or aren't interested.
next prev parent reply other threads:[~2026-07-24 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 5:05 [PATCH] xfs: fix nofs context corruption in xfs_btree_split_worker Yun Zhou
2026-07-20 8:35 ` Christoph Hellwig
2026-07-24 7:54 ` Zhou, Yun
2026-07-24 8:06 ` Christoph Hellwig [this message]
2026-07-24 8:14 ` Zhou, Yun
2026-07-24 13:42 ` Christoph Hellwig
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=amMdC5fvYcsFXNmA@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cem@kernel.org \
--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 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.