From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next *REBASED* to 2c0ff6151c7b
Date: Wed, 18 Mar 2026 11:09:55 +0100 [thread overview]
Message-ID: <abp5xbbTP82DAogh@nidhogg.toxiclabs.cc> (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 *REBASED*.
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:
2c0ff6151c7b Merge branch 'xfs-7.1-merge' into for-next
17 new commits:
Bill Wendling (1):
[e5966096d085] xfs: annotate struct xfs_attr_list_context with __counted_by_ptr
Carlos Maiolino (5):
[db8367f63b30] xfs: factor out isize updates from xfs_dio_write_end_io
[02a5d8993b09] xfs: factor out xfs_dio_write_zoned_end_io
[3bdc20b005c2] xfs: factor out xfs_zone_inc_written
[01478f356ff7] xfs: opencode xfs_zone_record_blocks
[2c0ff6151c7b] Merge branch 'xfs-7.1-merge' into for-next
Christoph Hellwig (1):
[0c98524ab201] xfs: cleanup buftarg handling in XFS_IOC_VERIFY_MEDIA
Damien Le Moal (4):
[770323d418ed] xfs: avoid unnecessary open zone check in xfs_select_zone_nowait()
[6a82a691b080] xfs: fix a comment typo in xfs_select_zone_nowait()
[68aa101bf204] xfs: display more zone related information in mountstats
[c1f955437440] xfs: avoid unnecessary calculations in xfs_zoned_need_gc()
Wilfred Mallawa (1):
[c6ce65cb17aa] xfs: add write pointer to xfs_rtgroup_geometry
Yuto Ohnuki (4):
[4f24a767e3d6] xfs: stop reclaim before pushing AIL during unmount
[79ef34ec0554] xfs: avoid dereferencing log items after push callbacks
[394d70b86fae] xfs: save ailp before dropping the AIL lock in push callbacks
[7cac60947335] xfs: refactor xfsaild_push loop into helper
hongao (1):
[268378b6ad20] xfs: scrub: unlock dquot before early return in quota scrub
Code Diffstat:
fs/xfs/libxfs/xfs_attr.h | 3 +-
fs/xfs/libxfs/xfs_fs.h | 5 +-
fs/xfs/scrub/quota.c | 4 +-
fs/xfs/xfs_dquot_item.c | 9 +++-
fs/xfs/xfs_file.c | 95 ++++++++++++++++++++++++----------
fs/xfs/xfs_handle.c | 2 +-
fs/xfs/xfs_inode_item.c | 9 +++-
fs/xfs/xfs_ioctl.c | 19 +++++++
fs/xfs/xfs_mount.c | 7 +--
fs/xfs/xfs_trace.h | 36 +++++++++++--
fs/xfs/xfs_trans_ail.c | 127 +++++++++++++++++++++++++++-------------------
fs/xfs/xfs_verify_media.c | 18 +++----
fs/xfs/xfs_xattr.c | 2 +-
fs/xfs/xfs_zone_alloc.c | 44 ++++++++--------
fs/xfs/xfs_zone_gc.c | 24 ++++++---
fs/xfs/xfs_zone_info.c | 7 ++-
16 files changed, 277 insertions(+), 134 deletions(-)
reply other threads:[~2026-03-18 10:09 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=abp5xbbTP82DAogh@nidhogg.toxiclabs.cc \
--to=cem@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