From: Chandan Babu R <chandanbabu@kernel.org>
To: chandanbabu@kernel.org
Cc: dchinner@redhat.com,djwong@kernel.org,hch@lst.de,linux-fsdevel@vger.kernel.org,linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to 6a94b1acda7e
Date: Tue, 23 Apr 2024 15:46:24 +0530 [thread overview]
Message-ID: <87bk60z8lm.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
https://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:
6a94b1acda7e xfs: reinstate delalloc for RT inodes (if sb_rextsize == 1)
17 new commits:
Christoph Hellwig (17):
[e78a3ce28331] xfs: move more logic into xfs_extent_busy_clear_one
[c37d6ed87462] xfs: unwind xfs_extent_busy_clear
[c0ac6cb251bd] xfs: remove the unused xfs_extent_busy_enomem trace event
[4887e5316382] xfs: compile out v4 support if disabled
[330c4f94b0d7] xfs: make XFS_TRANS_LOWMODE match the other XFS_TRANS_ definitions
[b7e23c0e2e3b] xfs: refactor realtime inode locking
[9871d0963751] xfs: free RT extents after updating the bmap btree
[de37dbd0ccc6] xfs: move RT inode locking out of __xfs_bunmapi
[5e1e4d4fc79c] xfs: block deltas in xfs_trans_unreserve_and_mod_sb must be positive
[f30f656e25eb] xfs: split xfs_mod_freecounter
[dc1b17a25c32] xfs: reinstate RT support in xfs_bmapi_reserve_delalloc
[7e77d57a1fea] xfs: cleanup fdblock/frextent accounting in xfs_bmap_del_extent_delay
[7099bd0f243f] xfs: support RT inodes in xfs_mod_delalloc
[727f8431638f] xfs: look at m_frextents in xfs_iomap_prealloc_size for RT allocations
[da2b9c3a8d2c] xfs: rework splitting of indirect block reservations
[bd1753d8c42b] xfs: stop the steal (of data blocks for RT indirect blocks)
[6a94b1acda7e] xfs: reinstate delalloc for RT inodes (if sb_rextsize == 1)
Please note that the patch "xfs: fix sparse warning in xfs_extent_busy_clear"
has been dropped now.
Code Diffstat:
fs/xfs/libxfs/xfs_ag.c | 4 +--
fs/xfs/libxfs/xfs_ag_resv.c | 24 ++++-----------
fs/xfs/libxfs/xfs_ag_resv.h | 2 +-
fs/xfs/libxfs/xfs_alloc.c | 4 +--
fs/xfs/libxfs/xfs_bmap.c | 152 +++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------------
fs/xfs/libxfs/xfs_rtbitmap.c | 57 +++++++++++++++++++++++++++++++++++
fs/xfs/libxfs/xfs_rtbitmap.h | 17 +++++++++++
fs/xfs/libxfs/xfs_shared.h | 6 ++--
fs/xfs/scrub/common.c | 1 +
fs/xfs/scrub/fscounters.c | 12 +++++---
fs/xfs/scrub/fscounters.h | 1 +
fs/xfs/scrub/fscounters_repair.c | 12 +++++++-
fs/xfs/scrub/repair.c | 5 +--
fs/xfs/xfs_extent_busy.c | 80 ++++++++++++++++++++++--------------------------
fs/xfs/xfs_fsmap.c | 4 +--
fs/xfs/xfs_fsops.c | 29 +++++-------------
fs/xfs/xfs_fsops.h | 2 +-
fs/xfs/xfs_inode.c | 3 +-
fs/xfs/xfs_iomap.c | 45 ++++++++++++++++++---------
fs/xfs/xfs_iops.c | 2 +-
fs/xfs/xfs_mount.c | 87 +++++++++++++++++++++++++++++++----------------------
fs/xfs/xfs_mount.h | 76 +++++++++++++++++++++++++++++++++++-----------
fs/xfs/xfs_rtalloc.c | 22 +++++---------
fs/xfs/xfs_super.c | 39 +++++++++++++++---------
fs/xfs/xfs_trace.h | 2 --
fs/xfs/xfs_trans.c | 63 ++++++++++++++++++++------------------
26 files changed, 439 insertions(+), 312 deletions(-)
next reply other threads:[~2024-04-23 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:16 Chandan Babu R [this message]
2024-04-23 22:45 ` [ANNOUNCE] xfs-linux: for-next updated to 6a94b1acda7e Dave Chinner
2024-04-23 23:58 ` Darrick J. Wong
2024-04-24 5:19 ` Chandan Babu R
2024-04-24 14:58 ` Darrick J. Wong
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=87bk60z8lm.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).