From: Matt Fleming <matt@readmodwrite.com>
To: linux-xfs@vger.kernel.org
Cc: Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Brian Foster <bfoster@redhat.com>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, kernel-team@cloudflare.com
Subject: [BUG] xfs: sparse inode allocation can trip i != 1 after AGFL growth
Date: Fri, 17 Jul 2026 14:04:29 +0100 [thread overview]
Message-ID: <20260717130429.1838767-1-matt@readmodwrite.com> (raw)
Hi,
We're hitting an XFS shutdown in the sparse inode allocation path on
6.18-based kernels. The xfstests reproducer below also fails on
v7.2-rc3. The failure looks like this:
```
[ 18.785047][ T580] XFS (loop0): Internal error i != 1 at line 3768 of file fs/xfs/libxfs/xfs_btree.c. Caller xfs_btree_insert+0x1b8/0x270
[ 18.786901][ T580] CPU: 6 UID: 0 PID: 580 Comm: krn1319-trigger Not tainted 6.18.37-cloudflare-2026.6.20 #1 PREEMPT(voluntary)
[ 18.786905][ T580] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014
[ 18.786907][ T580] Call Trace:
[ 18.786918][ T580] <TASK>
[ 18.786923][ T580] dump_stack_lvl+0x4b/0x70
[ 18.786930][ T580] xfs_corruption_error+0xac/0xc0
[ 18.786934][ T580] ? xfs_btree_insert+0x1b8/0x270
[ 18.786937][ T580] xfs_btree_insert+0x1ee/0x270
[ 18.786944][ T580] ? xfs_btree_insert+0x1b8/0x270
[ 18.786950][ T580] ? xfs_inobt_insert_sprec.constprop.0+0x88/0x2d0
[ 18.786953][ T580] xfs_inobt_insert_sprec.constprop.0+0x88/0x2d0
[ 18.786956][ T580] xfs_ialloc_ag_alloc+0x25e/0x610
[ 18.786960][ T580] osnoise_arch_unregister+0x210/0x210
[ 18.786964][ T580] ? xfs_trans_alloc_icreate+0x89/0x110
[ 18.786967][ T580] xfs_create+0x165/0x460
[ 18.786971][ T580] xfs_generic_create+0x301/0x390
[ 18.786975][ T580] ? d_splice_alias_ops+0x1a8/0x660
[ 18.786979][ T580] path_openat+0x10e5/0x13c0
[ 18.786984][ T580] do_filp_open+0xc7/0x170
[ 18.786987][ T580] ? _raw_spin_unlock+0xe/0x30
[ 18.786991][ T580] ? change_protection+0x89e/0x1840
[ 18.786995][ T580] ? __x64_sys_prctl+0x27b/0xda0
[ 18.786999][ T580] ? kmem_cache_alloc_noprof+0x354/0x5b0
[ 18.787002][ T580] ? __check_object_size+0x1d6/0x1f0
[ 18.787006][ T580] do_sys_openat2+0x6e/0xc0
[ 18.787010][ T580] __x64_sys_openat+0x61/0xa0
[ 18.787013][ T580] do_syscall_64+0x74/0xa00
[ 18.787018][ T580] ? flush_tlb_func+0x2be/0x340
[ 18.787021][ T580] ? mod_memcg_lruvec_state+0xc5/0x1f0
[ 18.787024][ T580] ? __lruvec_stat_mod_folio+0x97/0x130
[ 18.787027][ T580] ? __folio_mod_stat+0x2d/0x90
[ 18.787029][ T580] ? folio_add_new_anon_rmap+0xa1/0x360
[ 18.787032][ T580] ? _raw_spin_unlock+0xe/0x30
[ 18.787033][ T580] ? do_wp_page+0x5ee/0x13a0
[ 18.787036][ T580] ? __handle_mm_fault+0x8b3/0xdf0
[ 18.787040][ T580] ? count_memcg_events+0xc2/0x190
[ 18.787041][ T580] ? handle_mm_fault+0x19b/0x280
[ 18.787044][ T580] ? do_user_addr_fault+0x22a/0x6e0
[ 18.787046][ T580] ? exc_page_fault+0x8f/0x1b0
[ 18.787048][ T580] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 18.787051][ T580] RIP: 0033:0x4398d1
[ 18.787054][ T580] Code: 75 57 89 f0 25 00 00 41 00 3d 00 00 41 00 74 49 80 3d 9a e7 06 00 00 74 6d 89 da 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 93 00 00 00 48 8b 54 24 28 64 48 2b 14 25
[ 18.787056][ T580] RSP: 002b:00007ffd378317d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
[ 18.787059][ T580] RAX: ffffffffffffffda RBX: 00000000000800c1 RCX: 00000000004398d1
[ 18.787061][ T580] RDX: 00000000000800c1 RSI: 00007ffd37831860 RDI: 00000000ffffff9c
[ 18.787065][ T580] RBP: 00007ffd37831860 R08: 0000000000000000 R09: 0000000000000000
[ 18.787067][ T580] R10: 0000000000000180 R11: 0000000000000202 R12: 00007ffd37832a78
[ 18.787068][ T580] R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000003
[ 18.787070][ T580] </TASK>
[ 18.825732][ T580] XFS (loop0): Corruption detected. Unmount and run xfs_repair
[ 18.827101][ T580] XFS (loop0): invalid sparse inode record: ino 0x6500 holemask 0xff00 count 32
[ 18.828459][ T580] XFS (loop0): Corruption of in-memory data (0x8) detected at xfs_ialloc_ag_alloc+0x466/0x610 (fs/xfs/libxfs/xfs_ialloc.c:920). Shutting down filesystem.
[ 18.830702][ T580] XFS (loop0): Please unmount the filesystem and rectify the problem(s)
```
The sparse inode record does not appear to be corrupt. The problem looks
like an allocator invariant violation caused by AGFL requirements changing
between the sparse inode extent allocation and the subsequent inobt insert.
I have an xfstests reproducer here:
https://github.com/mfleming/xfstests-dev/commit/01a530256e47e15e4d54a08798fa3112067c793e
It formats the fs with:
```
mkfs.xfs -f -K \
-s size=4096 \
-m crc=1,finobt=1,rmapbt=1,reflink=1,inobtcount=1,bigtime=1 \
-i size=512,sparse=1,maxpct=25,nrext64=1 \
-d agcount=2,su=512k,sw=2 \
<loopdev>
```
The reproducer sets AG0 to this precondition immediately before the
final file create:
```
inobt leaf: 252/252 records
bnobt/cntbt: 505/505 records
AGFL: flcount=8, min_freelist=8
levels: bno/cnt/rmap = 1/1/2
free/reservation: xfs_db agresv free=2522, reservation=2505
pagf_freeblks: 2514 # xfs_db free includes AGFL blocks
available: 2514 + min(8, 8) - 2505 - 8 - 2 = 7
trigger extent: agbno=3330, len=8
```
The failure sequence seems to be:
1. AG0 has no free inodes, so inode allocation needs a new chunk.
2. Full chunk allocation cannot fit.
3. Sparse chunk allocation can fit and passes the old AGFL minimum check.
4. Removing the sparse extent from free space grows both bnobt and cntbt.
5. That raises `xfs_alloc_min_freelist()` and drains the AGFL.
6. The later inobt leaf split needs one ordinary block and gets no block.
7. The no-progress result becomes `i != 1` and is treated as corruption.
I think the sparse-inode logic was introduced by commit 56d1115c9bc7
("xfs: allocate sparse inode chunks on full chunk allocation failure").
rmapbt/per-AG reservations make this much easier to hit because most of an AG's
raw free space can be reserved for metadata growth, but the sparse inode path
above is what turns the allocation failure into a filesystem shutdown.
Thanks,
Matt
next reply other threads:[~2026-07-17 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:04 Matt Fleming [this message]
2026-07-17 17:55 ` [BUG] xfs: sparse inode allocation can trip i != 1 after AGFL growth Brian Foster
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=20260717130429.1838767-1-matt@readmodwrite.com \
--to=matt@readmodwrite.com \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@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