From: Dave Chinner <david@fromorbit.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-xfs@vger.kernel.org,
Chandan Babu R <chandan.babu@oracle.com>,
Leah Rumancik <lrumancik@google.com>
Subject: Re: xfs: bug fixes for 6.4-rcX
Date: Wed, 17 May 2023 21:34:33 +1000 [thread overview]
Message-ID: <ZGS7yaaI7knS0QdM@dread.disaster.area> (raw)
In-Reply-To: <CAOQ4uxiJ-sYPpGcPpVzz0hScUNdZ4bs8=GUsncNOXdeEAOCaCQ@mail.gmail.com>
On Wed, May 17, 2023 at 10:07:55AM +0300, Amir Goldstein wrote:
> On Wed, May 17, 2023 at 3:08 AM Dave Chinner <david@fromorbit.com> wrote:
> >
> > Hi folks,
> >
>
> Hi Dave,
>
> > The following patches are fixes for recently discovered problems.
> > I'd like to consider them all for a 6.4-rc merge, though really only
> > patch 2 is a necessary recent regression fix.
> >
> > The first patch addresses a long standing buffer UAF during shutdown
> > situations, where shutdown log item completions can race with CIL
> > abort and iclog log item completions.
> >
>
> Can you tell roughly how far back this UAF bug goes
> or is it long standing enough to be treated as "forever"?
Longer than I cared to trace the history back.
> > The second patch addresses a small performance regression from the
> > 6.3 allocator rewrite which is also a potential AGF-AGF deadlock
> > vector as it allows out-of-order locking.
> >
> > The third patch is a change needed by patch 4, which I split out for
> > clarity. By itself it does nothing.
> >
> > The fourth patch is a fix for a AGI->AGF->inode cluster buffer lock
> > ordering deadlock. This was introduced when we started pinning inode
> > cluster buffers in xfs_trans_log_inode() in 5.8 to fix long-standing
> > inode reclaim blocking issues, but I've only seen it in the wild
> > once on a system making heavy use of OVL and hence O_TMPFILE based
> > operations.
>
> Thank you for providing Fixes and this summary with backporing hints :)
I don't think you're going to be able to backport the inode cluster
buffer lock fix. Nothing prior to 5.19 has the necessary
infrastructure or the iunlink log item code this latest fix builds
on top of. That was done to fix a whole class of relatively easy to
hit O_TMPFILE related AGI-AGF-inode cluster buffer deadlocks. This
fix avoids an entirely different class of inode cluster buffer
deadlocks using the infrastructure introduced in the 5.19 deadlock
fixes.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-05-17 11:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 0:04 xfs: bug fixes for 6.4-rcX Dave Chinner
2023-05-17 0:04 ` [PATCH 1/4] xfs: buffer pins need to hold a buffer reference Dave Chinner
2023-05-17 1:26 ` Darrick J. Wong
2023-05-17 12:58 ` Christoph Hellwig
2023-05-17 22:24 ` Dave Chinner
2023-05-17 0:04 ` [PATCH 2/4] xfs: restore allocation trylock iteration Dave Chinner
2023-05-17 1:11 ` Darrick J. Wong
2023-05-17 12:59 ` Christoph Hellwig
2023-05-17 0:04 ` [PATCH 3/4] xfs: defered work could create precommits Dave Chinner
2023-05-17 1:20 ` Darrick J. Wong
2023-05-17 1:44 ` Dave Chinner
2023-06-01 15:01 ` Christoph Hellwig
2023-05-17 0:04 ` [PATCH 4/4] xfs: fix AGF vs inode cluster buffer deadlock Dave Chinner
2023-05-17 1:26 ` Darrick J. Wong
2023-05-17 1:47 ` Dave Chinner
2023-06-01 1:51 ` Dave Chinner
2023-06-01 14:38 ` Darrick J. Wong
2023-06-01 15:12 ` Christoph Hellwig
2023-06-25 2:58 ` Matthew Wilcox
2023-06-25 22:34 ` Dave Chinner
2023-05-17 7:07 ` xfs: bug fixes for 6.4-rcX Amir Goldstein
2023-05-17 11:34 ` Dave Chinner [this message]
2023-05-17 12:48 ` Amir Goldstein
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=ZGS7yaaI7knS0QdM@dread.disaster.area \
--to=david@fromorbit.com \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lrumancik@google.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