From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next rebased to d4d12c02bf5f
Date: Mon, 5 Jun 2023 15:07:20 +1000 [thread overview]
Message-ID: <ZH1tiD4z4/revqp3@dread.disaster.area> (raw)
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
fs/xfs/libxfs/xfs_ag.c | 5 +++-
fs/xfs/libxfs/xfs_alloc.c | 91 ++++++++++++++++++++++++++++++++++++++++++++++++++---------------------
fs/xfs/libxfs/xfs_alloc.h | 6 ++---
fs/xfs/libxfs/xfs_bmap.c | 10 ++++++--
fs/xfs/libxfs/xfs_bmap_btree.c | 7 ++++--
fs/xfs/libxfs/xfs_ialloc.c | 24 ++++++++++++-------
fs/xfs/libxfs/xfs_log_format.h | 9 ++++++-
fs/xfs/libxfs/xfs_refcount.c | 13 ++++++++---
fs/xfs/libxfs/xfs_trans_inode.c | 113 +++++++---------------------------------------------------------------------------------
fs/xfs/scrub/bmap.c | 25 ++++++++++----------
fs/xfs/scrub/scrub.h | 8 +++----
fs/xfs/xfs_buf_item.c | 88 ++++++++++++++++++++++++++++++++++++++++++++++++++------------------
fs/xfs/xfs_filestream.c | 1 -
fs/xfs/xfs_icache.c | 46 +++++++++++++++++++++++++++++-------
fs/xfs/xfs_icache.h | 4 ++--
fs/xfs/xfs_inode.c | 20 +++++-----------
fs/xfs/xfs_inode.h | 2 +-
fs/xfs/xfs_inode_item.c | 149 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_inode_item.h | 1 +
fs/xfs/xfs_log_recover.c | 19 +++++++--------
fs/xfs/xfs_mount.h | 1 +
fs/xfs/xfs_reflink.c | 4 +++-
fs/xfs/xfs_super.c | 1 +
fs/xfs/xfs_trans.c | 9 ++++++-
24 files changed, 427 insertions(+), 229 deletions(-)
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2023-06-05 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 5:07 Dave Chinner [this message]
2023-06-06 0:09 ` [ANNOUNCE] xfs: for-next rebased to d4d12c02bf5f Darrick J. Wong
2023-06-06 0:59 ` Dave Chinner
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=ZH1tiD4z4/revqp3@dread.disaster.area \
--to=david@fromorbit.com \
--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