Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sat, 29 May 2021 10:12:12 -0700
From:   "Darrick J. Wong" <djwong@kernel.org>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
        david@fromorbit.com, linux-kernel@vger.kernel.org,
        sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] xfs: fixes for 5.13-rc4
Message-ID: <20210529171212.GQ2402049@locust>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Precedence: bulk

Hi Linus,

Please pull this branch containing bug fixes for 5.13-rc4.  This week's
pile mitigates some decades-old problems in how extent size hints
interact with realtime volumes, fixes some failures in online shrink,
and fixes a problem where directory and symlink shrinking on extremely
fragmented filesystems could fail.

The most user-notable change here is to point users at our (new) IRC
channel on OFTC.  Freedom isn't free, it costs folks like you and me;
and if you don't kowtow, they'll expel everyone and take over your
channel.  (Ok, ok, that didn't fit the song lyrics...)

The branch merges cleanly against upstream as of a few minutes ago.
Please let me know if anything else strange happens during the merge
process.

--D

The following changes since commit e3c2b047475b52739bcf178a9e95176c42bbcf8f:

  xfs: restore old ioctl definitions (2021-05-20 08:31:22 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.13-fixes-3

for you to fetch changes up to 0fe0bbe00a6fb77adf75085b7d06b71a830dd6f2:

  xfs: bunmapi has unnecessary AG lock ordering issues (2021-05-27 08:11:24 -0700)

----------------------------------------------------------------
Fixes for 5.13-rc4:
- Fix a bug where unmapping operations end earlier than expected, which
  can cause chaos on multi-block directory and symlink shrink
  operations.
- Fix an erroneous assert that can trigger if we try to transition a
  bmap structure from btree format to extents format with zero extents.
  This was exposed by xfs/538.

----------------------------------------------------------------
Darrick J. Wong (4):
      xfs: check free AG space when making per-AG reservations
      xfs: standardize extent size hint validation
      xfs: validate extsz hints against rt extent size when rtinherit is set
      xfs: add new IRC channel to MAINTAINERS

Dave Chinner (2):
      xfs: btree format inode forks can have zero extents
      xfs: bunmapi has unnecessary AG lock ordering issues

 MAINTAINERS                     |   1 +
 fs/xfs/libxfs/xfs_ag_resv.c     |  18 +++++--
 fs/xfs/libxfs/xfs_bmap.c        |  12 -----
 fs/xfs/libxfs/xfs_inode_buf.c   |  46 ++++++++++++++++--
 fs/xfs/libxfs/xfs_trans_inode.c |  17 +++++++
 fs/xfs/xfs_inode.c              |  29 ++++++++++++
 fs/xfs/xfs_ioctl.c              | 101 ++++++++++++++--------------------------
 fs/xfs/xfs_message.h            |   2 +
 8 files changed, 140 insertions(+), 86 deletions(-)