From: "Darrick J. Wong" <djwong@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: transaction assertion failure in next-20251103
Date: Tue, 4 Nov 2025 08:01:02 -0800 [thread overview]
Message-ID: <20251104160102.GF196370@frogsfrogsfrogs> (raw)
In-Reply-To: <aQohjfEFmU8lef6M@casper.infradead.org>
On Tue, Nov 04, 2025 at 03:53:49PM +0000, Matthew Wilcox wrote:
> Two runs of xfstests, two assertion failures. One while running
> generic/083, one while running generic/561.
Can you also post the output of xfs_info /dev/vd[bc] (whichever one is
TEST_DEV)? 561 is the duperemove + write stress test, and 083 is
another stresser.
--D
> Here's the g/561 failure:
>
> generic/561 run fstests generic/561 at 2025-11-03 22:20:18
> XFS (vdb): Mounting V5 Filesystem e0d0d737-4733-4583-8d2e-deaedb725697
> XFS (vdb): Ending clean mount
> XFS (vdc): Mounting V5 Filesystem 522795a0-828a-4476-9928-c71a0ff20619
> XFS (vdc): Ending clean mount
> XFS (vdc): Unmounting Filesystem 522795a0-828a-4476-9928-c71a0ff20619
> XFS (vdc): Mounting V5 Filesystem 2a587011-9c3c-41df-b507-5d3b27f8616c
> XFS (vdc): Ending clean mount
> iomap_finish_ioend_buffered: 80 callbacks suppressed
> vdc: writeback error on inode 166, offset 1589248, sector 5544
> vdc: writeback error on inode 25165978, offset 3338240, sector 22021584
> vdc: writeback error on inode 174, offset 1327104, sector 14832056
> vdc: writeback error on inode 8388743, offset 1122304, sector 7342704
> vdc: writeback error on inode 8388743, offset 4091904, sector 7344688
> vdc: writeback error on inode 8388743, offset 7483392, sector 7362280
> vdc: writeback error on inode 16908430, offset 5103616, sector 22031648
> vdc: writeback error on inode 16908430, offset 5865472, sector 22033136
> vdc: writeback error on inode 16908438, offset 778240, sector 22031064
> vdc: writeback error on inode 16908438, offset 3309568, sector 22031216
> XFS (vdc): Corruption of in-memory data (0x8) detected at xfs_trans_mod_sb+0x2a4/0x310 (fs/xfs/xfs_trans.c:353). Shutting down filesystem.
> XFS (vdc): Please unmount the filesystem and rectify the problem(s)
> XFS: Assertion failed: tp->t_blk_res >= tp->t_blk_res_used, file: fs/xfs/xfs_trans.c, line: 120
> ------------[ cut here ]------------
> kernel BUG at fs/xfs/xfs_message.c:102!
> Oops: invalid opcode: 0000 [#1] SMP NOPTI
> CPU: 3 UID: 0 PID: 1631375 Comm: kworker/3:4 Tainted: G W 6.18.0-rc4-next-20251103-ktest-00016-g8c6f8121e488 #113 NONE
> Tainted: [W]=WARN
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
> Workqueue: xfs-conv/vdc xfs_end_io
> RIP: 0010:assfail+0x3c/0x46
> Code: c2 f8 d1 41 82 48 89 f1 48 89 fe 48 c7 c7 55 69 46 82 48 89 e5 e8 e4 fd ff ff 8a 05 e6 79 55 01 3c 01 76 02 0f 0b a8 01 74 02 <0f> 0b 0f 0b 5d c3 cc cc cc cc 48 8d 45 10 4c 8d 6c 24 10 48 89 e2
> RSP: 0018:ffff8881582d3ba8 EFLAGS: 00010202
> RAX: 00000000ffffff01 RBX: ffff8880174a9790 RCX: 000000007fffffff
> RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffffffff82466955
> RBP: ffff8881582d3ba8 R08: 0000000000000000 R09: 000000000000000a
> R10: 000000000000000a R11: 0fffffffffffffff R12: ffff8880174a9878
> R13: ffff888110460000 R14: 0000000000000000 R15: ffff8880174a9948
> FS: 0000000000000000(0000) GS:ffff8881f6b8d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f7098803000 CR3: 0000000155342000 CR4: 0000000000750eb0
> PKRU: 55555554
> Call Trace:
> <TASK>
> xfs_trans_dup+0x258/0x270
> xfs_trans_roll+0x48/0x120
> xfs_defer_trans_roll+0x5f/0x1a0
> xfs_defer_finish_noroll+0x3d5/0x5d0
> xfs_trans_commit+0x4e/0x70
> xfs_iomap_write_unwritten+0xe5/0x350
> xfs_end_ioend+0x219/0x2c0
> xfs_end_io+0xae/0xd0
> process_one_work+0x1ed/0x530
> ? move_linked_works+0x77/0xb0
> worker_thread+0x1cf/0x3d0
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x100/0x220
> ? _raw_spin_unlock_irq+0x2b/0x40
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x1f6/0x250
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1a/0x30
> </TASK>
> Modules linked in: [last unloaded: crc_t10dif]
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:assfail+0x3c/0x46
> Code: c2 f8 d1 41 82 48 89 f1 48 89 fe 48 c7 c7 55 69 46 82 48 89 e5 e8 e4 fd ff ff 8a 05 e6 79 55 01 3c 01 76 02 0f 0b a8 01 74 02 <0f> 0b 0f 0b 5d c3 cc cc cc cc 48 8d 45 10 4c 8d 6c 24 10 48 89 e2
> RSP: 0018:ffff8881582d3ba8 EFLAGS: 00010202
> RAX: 00000000ffffff01 RBX: ffff8880174a9790 RCX: 000000007fffffff
> RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffffffff82466955
> RBP: ffff8881582d3ba8 R08: 0000000000000000 R09: 000000000000000a
> R10: 000000000000000a R11: 0fffffffffffffff R12: ffff8880174a9878
> R13: ffff888110460000 R14: 0000000000000000 R15: ffff8880174a9948
> FS: 0000000000000000(0000) GS:ffff8881f6b8d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f7098803000 CR3: 0000000155342000 CR4: 0000000000750eb0
> PKRU: 55555554
> Kernel panic - not syncing: Fatal exception
> Kernel Offset: disabled
> ---[ end Kernel panic - not syncing: Fatal exception ]---
>
> The 081 failure looks similar:
>
> vdc: writeback error on inode 131223, offset 1552384, sector 194360
> XFS (vdc): Corruption of in-memory data (0x8) detected at xfs_trans_mod_sb+0x2a4
> /0x310 (fs/xfs/xfs_trans.c:353). Shutting down filesystem.
> XFS (vdc): Please unmount the filesystem and rectify the problem(s)
> XFS: Assertion failed: tp->t_blk_res >= tp->t_blk_res_used, file: fs/xfs/xfs_tra
> ns.c, line: 120
> ------------[ cut here ]------------
> kernel BUG at fs/xfs/xfs_message.c:102!
> Oops: invalid opcode: 0000 [#1] SMP NOPTI
> CPU: 3 UID: 0 PID: 338999 Comm: kworker/3:12 Not tainted 6.18.0-rc4-next-2025110
> 3-ktest-00016-g8c6f8121e488 #113 NONE
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2
> 04/01/2014
> Workqueue: xfs-conv/vdc xfs_end_io
> RIP: 0010:assfail+0x3c/0x46
> Code: c2 f8 d1 41 82 48 89 f1 48 89 fe 48 c7 c7 55 69 46 82 48 89 e5 e8 e4 fd ff ff 8a 05 e6 79 55 01 3c 01 76 02 0f 0b a8 01 74 02 <0f> 0b 0f 0b 5d c3 cc cc cc cc 48 8d 45 10 4c 8d 6c 24 10 48 89 e2
> RSP: 0018:ffff888115b3fba8 EFLAGS: 00010202
> RAX: 00000000ffffff01 RBX: ffff88815d857878 RCX: 000000007fffffff
> RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffffffff82466955
> RBP: ffff888115b3fba8 R08: 0000000000000000 R09: 000000000000000a
> R10: 000000000000000a R11: 0fffffffffffffff R12: ffff88815d857d00
> R13: ffff888114c28000 R14: 0000000000000000 R15: ffff88815d857dd0
> FS: 0000000000000000(0000) GS:ffff8881f6b8d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f585a04a000 CR3: 000000010ebd3000 CR4: 0000000000750eb0
> PKRU: 55555554
> Call Trace:
> <TASK>
> xfs_trans_dup+0x258/0x270
> xfs_trans_roll+0x48/0x120
> xfs_defer_trans_roll+0x5f/0x1a0
> xfs_defer_finish_noroll+0x3d5/0x5d0
> xfs_trans_commit+0x4e/0x70
> xfs_iomap_write_unwritten+0xe5/0x350
> xfs_end_ioend+0x219/0x2c0
> xfs_end_io+0xae/0xd0
> process_one_work+0x1ed/0x530
> ? move_linked_works+0x77/0xb0
> worker_thread+0x1cf/0x3d0
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x100/0x220
> ? _raw_spin_unlock_irq+0x2b/0x40
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x1f6/0x250
> ? __pfx_kthread+0x10/0x10
> ret_from_fork_asm+0x1a/0x30
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:assfail+0x3c/0x46
> Code: c2 f8 d1 41 82 48 89 f1 48 89 fe 48 c7 c7 55 69 46 82 48 89 e5 e8 e4 fd ff ff 8a 05 e6 79 55 01 3c 01 76 02 0f 0b a8 01 74 02 <0f> 0b 0f 0b 5d c3 cc cc cc cc 48 8d 45 10 4c 8d 6c 24 10 48 89 e2
> RSP: 0018:ffff888115b3fba8 EFLAGS: 00010202
> RAX: 00000000ffffff01 RBX: ffff88815d857878 RCX: 000000007fffffff
> RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffffffff82466955
> RBP: ffff888115b3fba8 R08: 0000000000000000 R09: 000000000000000a
> R10: 000000000000000a R11: 0fffffffffffffff R12: ffff88815d857d00
> R13: ffff888114c28000 R14: 0000000000000000 R15: ffff88815d857dd0
> FS: 0000000000000000(0000) GS:ffff8881f6b8d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f585a04a000 CR3: 000000010ebd3000 CR4: 0000000000750eb0
> PKRU: 55555554
> Kernel panic - not syncing: Fatal exception
> Kernel Offset: disabled
> ---[ end Kernel panic - not syncing: Fatal exception ]---
>
>
next prev parent reply other threads:[~2025-11-04 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:53 transaction assertion failure in next-20251103 Matthew Wilcox
2025-11-04 16:01 ` Darrick J. Wong [this message]
2025-11-04 16:19 ` Matthew Wilcox
2025-11-04 22:25 ` Dave Chinner
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=20251104160102.GF196370@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).