public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 8944c6fb8add
Date: Wed, 29 Jun 2022 08:52:52 -0700	[thread overview]
Message-ID: <Yrx1VOjVJriO+Iv0@magnolia> (raw)

Hi folks,

The for-next branch of the xfs-linux repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

has just been updated.

Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.  With willy's fix seeming to resolve the generic/522
corruptions, I think this will be the last push to 5.19, and I can begin
examining patches for 5.20.

The new head of the for-next branch is commit:

8944c6fb8add xfs: dont treat rt extents beyond EOF as eofblocks to be cleared

9 new commits:

Darrick J. Wong (5):
      [b822ea17fd15] xfs: always free xattri_leaf_bp when cancelling a deferred op
      [f94e08b602d4] xfs: clean up the end of xfs_attri_item_recover
      [7be3bd8856fb] xfs: empty xattr leaf header blocks are not corruption
      [e53bcffad032] xfs: don't hold xattr leaf buffers across transaction rolls
      [8944c6fb8add] xfs: dont treat rt extents beyond EOF as eofblocks to be cleared

Dave Chinner (2):
      [7cf2b0f9611b] xfs: bound maximum wait time for inodegc work
      [5e672cd69f0a] xfs: introduce xfs_inodegc_push()

Kaixu Xia (2):
      [ca76a761ea24] xfs: factor out the common lock flags assert
      [82af88063961] xfs: use invalidate_lock to check the state of mmap_lock

Code Diffstat:

 fs/xfs/libxfs/xfs_attr.c      | 38 ++++++-------------------
 fs/xfs/libxfs/xfs_attr.h      |  5 ----
 fs/xfs/libxfs/xfs_attr_leaf.c | 35 ++++++++++++-----------
 fs/xfs/libxfs/xfs_attr_leaf.h |  3 +-
 fs/xfs/xfs_attr_item.c        | 27 ++++++++++--------
 fs/xfs/xfs_bmap_util.c        |  2 ++
 fs/xfs/xfs_icache.c           | 56 ++++++++++++++++++++++++-------------
 fs/xfs/xfs_icache.h           |  1 +
 fs/xfs/xfs_inode.c            | 64 +++++++++++++++++--------------------------
 fs/xfs/xfs_mount.h            |  2 +-
 fs/xfs/xfs_qm_syscalls.c      |  9 ++++--
 fs/xfs/xfs_super.c            |  9 ++++--
 fs/xfs/xfs_trace.h            |  1 +
 13 files changed, 123 insertions(+), 129 deletions(-)

                 reply	other threads:[~2022-06-29 15:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Yrx1VOjVJriO+Iv0@magnolia \
    --to=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