From: Chandan Babu R <chandanbabu@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: fix unlink vs cluster buffer instantiation race
Date: Fri, 14 Jun 2024 18:00:44 +0530 [thread overview]
Message-ID: <87bk43wvr7.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <ZmwX91xXpuvPnPh7@infradead.org>
On Fri, Jun 14, 2024 at 03:14:15 AM -0700, Christoph Hellwig wrote:
> On Fri, Jun 14, 2024 at 03:31:23PM +0530, Chandan Babu R wrote:
>> I am planning to include this patch for v6.11 rather than for v6.10 since -rc4
>> is generally the last release candidate where we add new XFS fixes unless the
>> bug fix is critical. Also, linux-next won't have new releases until June 30th
>> i.e. the next linux-next release is on July 1st. Hence, we will miss out on
>> testing/usage of XFS changes from the community.
>
> It is "critical" in the sense of it fixes a long standing bug people
> had to hack around for months with things like this:
>
> http://git.infradead.org/?p=users/hch/xfs.git;a=commitdiff;h=ea8d9cd0eb485c53eac01a3cf8524278381c31ee
>
> it also is trivial in terms of code. Not including it would be a
> really strange decision.
Ok. I will add this to the queue for v6.10-rc5.
--
Chandan
prev parent reply other threads:[~2024-06-14 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 22:51 [PATCH] xfs: fix unlink vs cluster buffer instantiation race Dave Chinner
2024-06-13 13:35 ` Christoph Hellwig
2024-06-13 15:07 ` Darrick J. Wong
2024-06-14 10:01 ` Chandan Babu R
2024-06-14 10:14 ` Christoph Hellwig
2024-06-14 12:30 ` Chandan Babu R [this message]
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=87bk43wvr7.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/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