From: Carlos Maiolino <cem@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-xfs@vger.kernel.org
Subject: [GIT PULL] XFS: Fixes for v7.2-rc4
Date: Thu, 16 Jul 2026 18:06:09 +0200 [thread overview]
Message-ID: <alkAOxMdRvYOKSm2@nidhogg.toxiclabs.cc> (raw)
Hello Linus,
Could you please pull patches included in the tag below?
An attempt merge against your current TOT has been successful.
This contains mostly a series of bug fixes found by different LLM models
Thanks,
Carlos
"The following changes since commit e4281086ae6caf006b6ef0670479eb5f96880fb9:
xfs: simplify __xfs_buf_ioend (2026-07-01 12:29:50 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-fixes-7.2-rc4
for you to fetch changes up to 59c462b0f5cfa107794228051724b34ae9334168:
xfs: don't zap bmbt forks if they are MAXLEVELS tall (2026-07-14 11:01:47 +0200)
----------------------------------------------------------------
xfs: fixes for v7.2-rc4
Signed-off-by: Carlos Maiolino <cem@kernel.org>
----------------------------------------------------------------
Andrey Albershteyn (1):
xfs: fix null pointer dereference in tracepoint
Cen Zhang (1):
xfs: tie zoned sysfs lifetime to zone info
Darrick J. Wong (15):
xfs: resample the data fork mapping after cycling ILOCK
xfs: don't replace the wrong part of the cow fork
xfs: make cow repair somewhat flaky when debugging knob enabled
xfs: move cow_replace_mapping to xfs_bmap_util.c
xfs: don't wrap around quota ids in dqiterate
xfs: use rtrefcount btree cursor in xchk_xref_is_rt_cow_staging
xfs: use the rt version of the cow staging checker
xfs: write the rg superblock when fixing it
xfs: grab rtrmap btree when checking rgsuper
xfs: set xfarray killable sort correctly
xfs: fix off-by-one error when calling xchk_xref_has_rt_owner
xfs: handle non-inode owners for rtrmap record checking
xfs: fully check the parent handle when it points to the rootdir
xfs: clamp timestamp nanoseconds correctly
xfs: don't zap bmbt forks if they are MAXLEVELS tall
Jinliang Zheng (1):
xfs: use xfs_csn_t for xlog_cil_push_now() push_seq parameter
Weiming Shi (3):
xfs: drop ASSERT(0) on unrecognized log item type
xfs: splice unsorted log items back to the transaction after the loop
xfs: fail recovery on a committed log item with no regions
fs/xfs/libxfs/xfs_defer.c | 2 +-
fs/xfs/scrub/cow_repair.c | 177 +++++++++++++++++++++-----------------------
fs/xfs/scrub/dirtree.c | 16 ++--
fs/xfs/scrub/dqiterate.c | 2 +-
fs/xfs/scrub/inode_repair.c | 4 +-
fs/xfs/scrub/rgsuper.c | 14 +++-
fs/xfs/scrub/rtbitmap.c | 2 +-
fs/xfs/scrub/rtrefcount.c | 2 +-
fs/xfs/scrub/rtrmap.c | 8 +-
fs/xfs/scrub/scrub.h | 6 +-
fs/xfs/scrub/trace.h | 35 ---------
fs/xfs/scrub/xfarray.c | 3 +-
fs/xfs/xfs_bmap_util.c | 89 ++++++++++++++++++++++
fs/xfs/xfs_bmap_util.h | 4 +
fs/xfs/xfs_log_cil.c | 2 +-
fs/xfs/xfs_log_recover.c | 26 +++++--
fs/xfs/xfs_reflink.c | 36 +++++++++
fs/xfs/xfs_sysfs.c | 28 ++++---
fs/xfs/xfs_sysfs.h | 2 +
fs/xfs/xfs_trace.h | 41 ++++++++++
fs/xfs/xfs_zone_alloc.c | 8 ++
21 files changed, 339 insertions(+), 168 deletions(-)"
next reply other threads:[~2026-07-16 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 16:06 Carlos Maiolino [this message]
2026-07-16 17:26 ` [GIT PULL] XFS: Fixes for v7.2-rc4 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=alkAOxMdRvYOKSm2@nidhogg.toxiclabs.cc \
--to=cem@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--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