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-rc7
Date: Thu, 6 Aug 2026 11:18:11 +0200 [thread overview]
Message-ID: <anRAZ3k7id6zqYh-@andromeda.toxiclabs.cc> (raw)
Hello Linus,
Could you please pull patches included in the tag below?
This contains mostly a collection of bug fixes found by LLM tools.
An attempt merge against your current TOT has been successful.
Thanks,
Carlos
"The following changes since commit 59c462b0f5cfa107794228051724b34ae9334168:
xfs: don't zap bmbt forks if they are MAXLEVELS tall (2026-07-14 11:01:47 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-fixes-7.2-rc7
for you to fetch changes up to eb6b2cc1fc8ad566d746d128a559989ff0bba5cc:
xfs: check v5 superblock features early (2026-08-03 10:30:28 +0200)
----------------------------------------------------------------
xfs: fixes for 7.2-rc7
Signed-off-by: Carlos Maiolino <cem@kernel.org>
----------------------------------------------------------------
Andrey Albershteyn (1):
xfs: fix inverted clearance of inode junk flags
Christoph Hellwig (4):
xfs: update BDI {io,ra}_pages values based on the RT device limits
xfs: add a separate bio_set for spliting GC writes
xfs: add a comment to describe xfs_gc_bio.victim_rtg
xfs: check v5 superblock features early
Darrick J. Wong (21):
xfs: check cowextsize in xrep_inode_cowextsize
xfs: fix transaction block reservation in xrep_rtbitmap
xfs: rtsummary scrub should treat rtbitmap corruption errors as an xref error
xfs: zero i_nlink before repair puts inode on unlinked list
xfs: mark nonzero sb_gquotino as corrupt on metadir filesystems
xfs: only check mergeability of bnobt records
xfs: don't double-lock when deleting a self-referential directory
xfs: don't return EFSCORRUPTED when scrubbing corrupt parent pointers
xfs: don't zap the attr fork on repair when there are queued pptr updates
xfs: nlink scrub must take IOLOCK before determining ILOCK state
xfs: avoid UAF on sc->tempip in xrep_tempfile_create
xfs: hoist per-bucket unlinked list check to helper
xfs: don't livelock in scrub on a circular unlinked list
xfs: don't walk off the end of a null sc->sa.agi_bp in AGI repair
xfs: load next_agino from the correct xfarray in xrep_iunlink_relink_prev
xfs: pass runtime errors from xrep_iunlink_mark_ondisk_rec up to callers
xfs: check xfarray iteration errors when committing unlinked inode lists
xfs: fix allocated inodes that show up in the unlinked list
xfs: fix another iunlink infinite loop bug in online fsck
xfs: set the prev pointer when reinserting an inode on the unlinked list
xfs: don't ignore runtime errors in xrep_iunlink_reload_next
Guanghui Yang (1):
xfs: propagate errors from xfs_rtginode_load
Ibrahim Hashimov (1):
xfs: bounds-check buffer log item's dirty bitmap
Lin Jiapeng (1):
xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN
Long Li (2):
xfs: fix ilock leak on error in xfs_dq_get_next_id
xfs: don't swallow dquot recovery verification errors
Qiang Ma (1):
xfs: clear zapped attr fork state when bmap repair finds no attr fork
Xiang Mei (1):
xfs: fix off-by-one in rtrefcount btree root level validation
Yun Zhou (1):
xfs: handle NULL b_addr in xfs_buf_free
fs/xfs/libxfs/xfs_exchmaps.c | 10 +++
fs/xfs/libxfs/xfs_rtrefcount_btree.c | 4 +-
fs/xfs/libxfs/xfs_sb.c | 4 +-
fs/xfs/scrub/agheader.c | 98 ++++++++++++++------
fs/xfs/scrub/agheader_repair.c | 169 +++++++++++++++++++++++++++++------
fs/xfs/scrub/alloc.c | 5 +-
fs/xfs/scrub/attr_repair.c | 3 +-
fs/xfs/scrub/bmap.c | 5 ++
fs/xfs/scrub/dirtree_repair.c | 22 ++++-
fs/xfs/scrub/inode_repair.c | 6 +-
fs/xfs/scrub/nlinks.c | 13 +--
fs/xfs/scrub/nlinks_repair.c | 7 +-
fs/xfs/scrub/parent.c | 2 +-
fs/xfs/scrub/rtbitmap_repair.c | 46 ++++++----
fs/xfs/scrub/rtsummary.c | 2 +-
fs/xfs/scrub/tempfile.c | 1 +
fs/xfs/scrub/trace.h | 2 +
fs/xfs/xfs_buf.c | 2 +-
fs/xfs/xfs_buf_item_recover.c | 57 ++++++++----
fs/xfs/xfs_dquot.c | 3 +-
fs/xfs/xfs_dquot_item_recover.c | 2 +-
fs/xfs/xfs_mount.h | 7 ++
fs/xfs/xfs_rtalloc.c | 2 +-
fs/xfs/xfs_super.c | 53 ++++++++++-
fs/xfs/xfs_zone_gc.c | 13 ++-
25 files changed, 421 insertions(+), 117 deletions(-)"
next reply other threads:[~2026-08-06 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:18 Carlos Maiolino [this message]
2026-08-06 16:01 ` [GIT PULL] XFS: Fixes for v7.2-rc7 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=anRAZ3k7id6zqYh-@andromeda.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