All of
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <>
To: Linus Torvalds <>
	fstests <>
Subject: [GIT PULL] xfs: bug fixes for 5.19-rc5
Date: Sun, 3 Jul 2022 08:05:34 -0700	[thread overview]
Message-ID: <YsGwPqUYSW/IwgkN@magnolia> (raw)

Hi Linus,

Please pull this branch containing bug fixes for XFS for 5.19-rc5.  The
patches in this branch fix some stalling problems and correct the last
of the problems (I hope) observed during testing of the new atomic xattr
update feature.

As usual, I did a test-merge with upstream master as of a few minutes
ago, and it completed flawlessly.  Please let me know if you encounter
any problems.


The following changes since commit e89ab76d7e2564c65986add3d634cc5cf5bacf14:

  xfs: preserve DIFLAG2_NREXT64 when setting other inode attributes (2022-06-15 23:13:33 -0700)

are available in the Git repository at:

  git:// tags/xfs-5.19-fixes-4

for you to fetch changes up to 7561cea5dbb97fecb952548a0fb74fb105bf4664:

  xfs: prevent a UAF when log IO errors race with unmount (2022-07-01 09:09:52 -0700)

Fixes for 5.19-rc5:
 - Fix statfs blocking on background inode gc workers
 - Fix some broken inode lock assertion code
 - Fix xattr leaf buffer leaks when cancelling a deferred xattr update
 - Clean up xattr recovery to make it easier to understand.
 - Fix xattr leaf block verifiers tripping over empty blocks.
 - Remove complicated and error prone xattr leaf block bholding mess.
 - Fix a bug where an rt extent crossing EOF was treated as "posteof"
   blocks and cleaned unnecessarily.
 - Fix a UAF when log shutdown races with unmount.

Darrick J. Wong (6):
      xfs: always free xattri_leaf_bp when cancelling a deferred op
      xfs: clean up the end of xfs_attri_item_recover
      xfs: empty xattr leaf header blocks are not corruption
      xfs: don't hold xattr leaf buffers across transaction rolls
      xfs: dont treat rt extents beyond EOF as eofblocks to be cleared
      xfs: prevent a UAF when log IO errors race with unmount

Dave Chinner (2):
      xfs: bound maximum wait time for inodegc work
      xfs: introduce xfs_inodegc_push()

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

 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_log.c              |  9 ++++--
 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 +
 14 files changed, 130 insertions(+), 131 deletions(-)

             reply	other threads:[~2022-07-03 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 15:05 Darrick J. Wong [this message]
2022-07-03 16:51 ` pr-tracker-bot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YsGwPqUYSW/IwgkN@magnolia \ \ \ \ \ \ \ \ \ \
    --subject='Re: [GIT PULL] xfs: bug fixes for 5.19-rc5' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.