From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfs: for-next rebased to d4d12c02bf5f
Date: Tue, 6 Jun 2023 10:59:35 +1000 [thread overview]
Message-ID: <ZH6E9+5uZNbnc4G3@dread.disaster.area> (raw)
In-Reply-To: <20230606000951.GK1325469@frogsfrogsfrogs>
On Mon, Jun 05, 2023 at 05:09:51PM -0700, Darrick J. Wong wrote:
> On Mon, Jun 05, 2023 at 03:07:20PM +1000, Dave Chinner wrote:
> > Hi folks,
> >
> > I just rebased the for-next tree to correct a bad fixes tag in
> > the tree that was flags by a linux-next sanity check. The code is
> > the same, just a commit message needed rewriting, but that means all
> > the commit change and you'll need to do forced update if you pulled
> > the branch I pushed a few hours ago.
> >
> > -Dave.
> >
> > ----------------------------------------------------------------
> >
> > git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git for-next
> >
> > Head Commit: d4d12c02bf5f768f1b423c7ae2909c5afdfe0d5f
> >
> > xfs: collect errors from inodegc for unlinked inode recovery (2023-06-05 14:48:15 +1000)
> >
> > ----------------------------------------------------------------
> > Darrick J. Wong (1):
> > xfs: fix broken logic when detecting mergeable bmap records
> >
> > Dave Chinner (9):
> > xfs: buffer pins need to hold a buffer reference
> > xfs: restore allocation trylock iteration
> > xfs: defered work could create precommits
> > xfs: fix AGF vs inode cluster buffer deadlock
> > xfs: fix double xfs_perag_rele() in xfs_filestream_pick_ag()
> > xfs: fix agf/agfl verification on v4 filesystems
> > xfs: validity check agbnos on the AGFL
> > xfs: validate block number being freed before adding to xefi
> > xfs: collect errors from inodegc for unlinked inode recovery
> >
> > Geert Uytterhoeven (1):
> > xfs: Fix undefined behavior of shift into sign bit
>
> Hmm, I don't see "xfs: fix ag count overflow during growfs" in here.
No, I didn't pick it up because it conflicted with other bug fix
stuff I am currently working on and I needed to look at it in more
detail before doing anything with it. I hadn't followed the
development of the patch at all, and it was up to v4 so I was going
to need to spend a little bit of time on it to see what the history
of it was first....
> Dave, do you want to do another 6.4 bug release, or throw things back
> over the wall so I can merge all the rest of the pending fixes for 6.5?
If you want, you can pick it up once I've sent a pull request for
the current set of fixes in for-next. That will be later this week;
it needs to spend a couple of days in linux-next before that
happens, though.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-06-06 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 5:07 [ANNOUNCE] xfs: for-next rebased to d4d12c02bf5f Dave Chinner
2023-06-06 0:09 ` Darrick J. Wong
2023-06-06 0:59 ` Dave Chinner [this message]
2023-06-06 3:58 ` Darrick J. Wong
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=ZH6E9+5uZNbnc4G3@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.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