From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs-linux: for-next updated to 0877338ade31
Date: Mon, 10 Aug 2026 13:55:26 +0200 [thread overview]
Message-ID: <anm7ibwkbXHILA7r@andromeda.toxiclabs.cc> (raw)
Hi folks,
The for-next branch of the xfs-linux repository at:
gitolite.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:
0877338ade31 Merge branch 'xfs-7.3-merge' into for-next
17 new commits:
Carlos Maiolino (1):
[0877338ade31] Merge branch 'xfs-7.3-merge' into for-next
Christoph Hellwig (12):
[45fd506c334c] xfs: don't get a pag reference in xfs_buf_get_map
[568c8798a3d0] xfs: consolidate buffer locking in xfs_buf_get_map
[b6ba780af010] xfs: split out a lower-level xfs_buf_get_map helper from xfs_find_get_buf
[7a4eae80b5b3] xfs: remove spurious XBF_DONE clearing on readahead validation failure
[d80fe85bb2fc] xfs: remove _XBF_LOGRECOVERY
[9f224de410d7] xfs: hide b_flags manipulation from code outside of xfs_buf.c
[b15f6520ab64] xfs: use WRITE_ONCE to update b_flags
[3d102727432b] xfs: don't reverify buffers in xfs_buf_readahead_map
[819f1cc98aaf] xfs: use goto based error unwinding in xfs_buf_read_map
[21cc7775ee5c] xfs: merge xfs_buf_reverify into xfs_buf_read_map
[2aedf844be1d] xfs: move buffer locking out of xfs_find_get_buf
[00f40876f417] xfs: add lockless xfs_buf_readahead_map fast path
Hongling Zeng (3):
[a94e648f03cf] xfs: use file target for post-log fsync fallback flush
[6e6a31401445] xfs: check split_sectors validity before bio_split call
[b7eea80be25f] xfs: validate attr entry pointer before field access
Yun Zhou (1):
[0241ea5fb0fe] xfs: restore nofs context unconditionally in xfs_trans_roll
Code Diffstat:
fs/xfs/libxfs/xfs_attr_leaf.c | 14 ++
fs/xfs/libxfs/xfs_btree_staging.c | 7 +-
fs/xfs/libxfs/xfs_dquot_buf.c | 8 +-
fs/xfs/libxfs/xfs_ialloc.c | 2 +-
fs/xfs/libxfs/xfs_inode_buf.c | 15 +-
fs/xfs/xfs_buf.c | 392 ++++++++++++++++++++------------------
fs/xfs/xfs_buf.h | 8 +-
fs/xfs/xfs_buf_item.c | 10 +-
fs/xfs/xfs_buf_item_recover.c | 3 -
fs/xfs/xfs_dquot_item_recover.c | 1 -
fs/xfs/xfs_file.c | 26 ++-
fs/xfs/xfs_fsops.c | 2 +-
fs/xfs/xfs_inode.c | 4 +-
fs/xfs/xfs_inode_item_recover.c | 1 -
fs/xfs/xfs_log_recover.c | 5 +-
fs/xfs/xfs_trace.h | 2 +-
fs/xfs/xfs_trans.c | 16 +-
fs/xfs/xfs_trans_buf.c | 7 +-
fs/xfs/xfs_zone_gc.c | 2 +-
19 files changed, 279 insertions(+), 246 deletions(-)
reply other threads:[~2026-08-10 11:55 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=anm7ibwkbXHILA7r@andromeda.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