From: "Darrick J. Wong" <djwong@kernel.org>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: for-next updated to 0fe0bbe00a6f
Date: Thu, 27 May 2021 09:52:36 -0700 [thread overview]
Message-ID: <20210527165236.GF202121@locust> (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.
The new head of the for-next branch is commit:
0fe0bbe00a6f xfs: bunmapi has unnecessary AG lock ordering issues
New Commits:
Darrick J. Wong (4):
[0f9342513cc7] xfs: check free AG space when making per-AG reservations
[6b69e485894b] xfs: standardize extent size hint validation
[603f000b15f2] xfs: validate extsz hints against rt extent size when rtinherit is set
[9f5815315e0b] xfs: add new IRC channel to MAINTAINERS
Dave Chinner (2):
[991c2c5980fb] xfs: btree format inode forks can have zero extents
[0fe0bbe00a6f] xfs: bunmapi has unnecessary AG lock ordering issues
Code Diffstat:
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(-)
reply other threads:[~2021-05-27 16:52 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=20210527165236.GF202121@locust \
--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