linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: stable@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH, STABLE 6.3.x] xfs: fix livelock in delayed allocation at ENOSPC
Date: Sun, 28 May 2023 08:01:20 +0100	[thread overview]
Message-ID: <2023052807-chasing-same-5643@gregkh> (raw)
In-Reply-To: <ZHKB/KD1yyx77fop@dread.disaster.area>

On Sun, May 28, 2023 at 08:19:40AM +1000, Dave Chinner wrote:
> Hi Greg,
> 
> A regression in 6.3.0 has been identified in XFS that causes
> filesystem corruption.  It has been seen in the wild by a number of
> users, and bisected down to an issued we'd already fixed in 6.4-rc1
> with commit:
> 
> 9419092fb263 ("xfs: fix livelock in delayed allocation at ENOSPC")
> 
> This was reported with much less harmful symptoms (alloctor
> livelock) and it wasn't realised that it could have other, more
> impactful symptoms. A reproducer for the corruption was found
> yesterday and, soon after than, the cause of the corruption reports
> was identified.
> 
> The commit applies cleanly to a 6.3.0 kernel here, so it should also
> apply cleanly to a current 6.3.x kernel. I've included the entire
> commit below in case that's easier for you.
> 
> Can you please pull this commit into the next 6.3.x release as a
> matter of priority?

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-05-28  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 22:19 [PATCH, STABLE 6.3.x] xfs: fix livelock in delayed allocation at ENOSPC Dave Chinner
2023-05-28  7:01 ` Greg KH [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=2023052807-chasing-same-5643@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).