From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [GIT PULL] xfs: bug fix for 6.10
Date: Sat, 22 Jun 2024 09:05:02 -0700 [thread overview]
Message-ID: <20240622160502.GA3058325@frogsfrogsfrogs> (raw)
In-Reply-To: <20240622160058.GZ3058325@frogsfrogsfrogs>
On Sat, Jun 22, 2024 at 09:00:58AM -0700, Darrick J. Wong wrote:
> On Sat, Jun 22, 2024 at 07:05:49PM +0530, Chandan Babu R wrote:
> > Hi Linus,
>
> Drat, I ran the wrong script, please ignore this email, Linus.
> I guess I now have weekend work to go figure out why this happened.
Wait, no this is Chandan's PR to Linus, not the one I just tried to send
to Chandan. Sigh.
EVERYONE: ignore this email please.
--D
>
> > Please pull this branch which contains an XFS bug fix for 6.10-rc5. A brief
> > description of the bug fix is provided below.
>
> Chandan: Would _you_ mind pulling this branch with 6.10 fixes and
> sending them on to Linus?
>
> --D
>
> >
> > I did a test-merge with the main upstream branch as of a few minutes ago and
> > didn't see any conflicts. Please let me know if you encounter any problems.
> >
> > The following changes since commit 6ba59ff4227927d3a8530fc2973b80e94b54d58f:
> >
> > Linux 6.10-rc4 (2024-06-16 13:40:16 -0700)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.10-fixes-4
> >
> > for you to fetch changes up to 348a1983cf4cf5099fc398438a968443af4c9f65:
> >
> > xfs: fix unlink vs cluster buffer instantiation race (2024-06-17 11:17:09 +0530)
> >
> > ----------------------------------------------------------------
> > Bug fixes for 6.10-rc5:
> >
> > * Fix assertion failure due to a race between unlink and cluster buffer
> > instantiation.
> >
> > Signed-off-by: Chandan Babu R <chandanbabu@kernel.org>
> >
> > ----------------------------------------------------------------
> > Dave Chinner (1):
> > xfs: fix unlink vs cluster buffer instantiation race
> >
> > fs/xfs/xfs_inode.c | 23 +++++++++++++++++++----
> > 1 file changed, 19 insertions(+), 4 deletions(-)
> >
>
next prev parent reply other threads:[~2024-06-22 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 13:35 [GIT PULL] xfs: bug fix for 6.10 Chandan Babu R
2024-06-22 16:00 ` Darrick J. Wong
2024-06-22 16:04 ` Linus Torvalds
2024-06-22 16:05 ` Darrick J. Wong [this message]
2024-06-22 16:08 ` Linus Torvalds
2024-06-22 16:10 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-06-15 16:00 Chandan Babu R
2024-06-15 19:15 ` pr-tracker-bot
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=20240622160502.GA3058325@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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