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
Date: Sat, 29 May 2021 10:12:12 -0700 [thread overview]
Message-ID: <20210529171212.GQ2402049@locust> (raw)
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(-)
next reply other threads:[~2021-05-29 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 17:12 Darrick J. Wong [this message]
2021-05-30 4:30 ` 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:
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=20210529171212.GQ2402049@locust \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®