From: syzbot <syzbot+5f5f36a9ed0aadd614f3@syzkaller.appspotmail.com>
To: cem@kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] possible deadlock in xfs_buffered_write_iomap_begin
Date: Sun, 07 Dec 2025 15:10:24 -0800 [thread overview]
Message-ID: <69360960.a70a0220.38f243.006f.GAE@google.com> (raw)
In-Reply-To: <693377bd.a70a0220.243dc6.0023.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 37bb2e7217b0 Merge tag 'staging-6.19-rc1' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17992eb4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cf15a4b50e1152e3
dashboard link: https://syzkaller.appspot.com/bug?extid=5f5f36a9ed0aadd614f3
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=119ad21a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c96992580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-37bb2e72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/81ecfc98ace2/vmlinux-37bb2e72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e99cf6c2ce3/bzImage-37bb2e72.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/e65cf8e90d15/mount_1.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=11fce6c2580000)
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/aa9270f8ef66/mount_5.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=11380a1a580000)
mounted in repro #3: https://storage.googleapis.com/syzbot-assets/a3fc66ae7424/mount_14.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=169ad21a580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5f5f36a9ed0aadd614f3@syzkaller.appspotmail.com
XFS (loop0): Ending clean mount
XFS (loop0): Quotacheck needed: Please wait.
XFS (loop0): Quotacheck: Done.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/5508 is trying to acquire lock:
ffffffff8e251780 (fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:317 [inline]
ffffffff8e251780 (fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slub.c:4899 [inline]
ffffffff8e251780 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:5234 [inline]
ffffffff8e251780 (fs_reclaim){+.+.}-{0:0}, at: __kmalloc_cache_noprof+0x40/0x700 mm/slub.c:5766
but task is already holding lock:
ffff88804779d798 (&xfs_nondir_ilock_class){++++}-{4:4}, at: xfs_ilock_for_iomap fs/xfs/xfs_iomap.c:789 [inline]
ffff88804779d798 (&xfs_nondir_ilock_class){++++}-{4:4}, at: xfs_buffered_write_iomap_begin+0x4d1/0x1a70 fs/xfs/xfs_iomap.c:1793
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&xfs_nondir_ilock_class){++++}-{4:4}:
down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1706
xfs_reclaim_inode fs/xfs/xfs_icache.c:1035 [inline]
xfs_icwalk_process_inode fs/xfs/xfs_icache.c:1727 [inline]
xfs_icwalk_ag+0x1229/0x1a90 fs/xfs/xfs_icache.c:1809
xfs_icwalk fs/xfs/xfs_icache.c:1857 [inline]
xfs_reclaim_inodes_nr+0x1e3/0x260 fs/xfs/xfs_icache.c:1101
super_cache_scan+0x41b/0x4b0 fs/super.c:228
do_shrink_slab+0x6df/0x10d0 mm/shrinker.c:437
shrink_slab+0xd74/0x10d0 mm/shrinker.c:664
shrink_one+0x2d9/0x720 mm/vmscan.c:4919
shrink_many mm/vmscan.c:4980 [inline]
lru_gen_shrink_node mm/vmscan.c:5058 [inline]
shrink_node+0x2f7d/0x35b0 mm/vmscan.c:6045
kswapd_shrink_node mm/vmscan.c:6899 [inline]
balance_pgdat mm/vmscan.c:7082 [inline]
kswapd+0x145a/0x2820 mm/vmscan.c:7352
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
-> #0 (fs_reclaim){+.+.}-{0:0}:
check_prev_add kernel/locking/lockdep.c:3165 [inline]
check_prevs_add kernel/locking/lockdep.c:3284 [inline]
validate_chain kernel/locking/lockdep.c:3908 [inline]
__lock_acquire+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868
__fs_reclaim_acquire mm/page_alloc.c:4301 [inline]
fs_reclaim_acquire+0x72/0x100 mm/page_alloc.c:4315
might_alloc include/linux/sched/mm.h:317 [inline]
slab_pre_alloc_hook mm/slub.c:4899 [inline]
slab_alloc_node mm/slub.c:5234 [inline]
__kmalloc_cache_noprof+0x40/0x700 mm/slub.c:5766
kmalloc_noprof include/linux/slab.h:957 [inline]
iomap_fill_dirty_folios+0xf4/0x260 fs/iomap/buffered-io.c:1557
xfs_buffered_write_iomap_begin+0xa23/0x1a70 fs/xfs/xfs_iomap.c:1857
iomap_iter+0x5ef/0xeb0 fs/iomap/iter.c:110
iomap_zero_range+0x1cc/0xa30 fs/iomap/buffered-io.c:1590
xfs_zero_range+0x9a/0x100 fs/xfs/xfs_iomap.c:2289
xfs_free_file_space+0x8ad/0xcc0 fs/xfs/xfs_bmap_util.c:900
__xfs_file_fallocate+0x568/0x15f0 fs/xfs/xfs_file.c:1387
xfs_file_fallocate+0x27b/0x340 fs/xfs/xfs_file.c:1462
vfs_fallocate+0x669/0x7e0 fs/open.c:339
ksys_fallocate fs/open.c:363 [inline]
__do_sys_fallocate fs/open.c:368 [inline]
__se_sys_fallocate fs/open.c:366 [inline]
__x64_sys_fallocate+0xc0/0x110 fs/open.c:366
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&xfs_nondir_ilock_class);
lock(fs_reclaim);
lock(&xfs_nondir_ilock_class);
lock(fs_reclaim);
*** DEADLOCK ***
4 locks held by syz.0.17/5508:
#0: ffff88803d5a2420 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2681 [inline]
#0: ffff88803d5a2420 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0 fs/open.c:338
#1: ffff88804779d9b0 (&sb->s_type->i_mutex_key#25){++++}-{4:4}, at: xfs_ilock+0xee/0x370 fs/xfs/xfs_inode.c:149
#2: ffff88804779db50 (mapping.invalidate_lock#3){++++}-{4:4}, at: xfs_ilock+0x16c/0x370 fs/xfs/xfs_inode.c:157
#3: ffff88804779d798 (&xfs_nondir_ilock_class){++++}-{4:4}, at: xfs_ilock_for_iomap fs/xfs/xfs_iomap.c:789 [inline]
#3: ffff88804779d798 (&xfs_nondir_ilock_class){++++}-{4:4}, at: xfs_buffered_write_iomap_begin+0x4d1/0x1a70 fs/xfs/xfs_iomap.c:1793
stack backtrace:
CPU: 0 UID: 0 PID: 5508 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2043
check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
check_prev_add kernel/locking/lockdep.c:3165 [inline]
check_prevs_add kernel/locking/lockdep.c:3284 [inline]
validate_chain kernel/locking/lockdep.c:3908 [inline]
__lock_acquire+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868
__fs_reclaim_acquire mm/page_alloc.c:4301 [inline]
fs_reclaim_acquire+0x72/0x100 mm/page_alloc.c:4315
might_alloc include/linux/sched/mm.h:317 [inline]
slab_pre_alloc_hook mm/slub.c:4899 [inline]
slab_alloc_node mm/slub.c:5234 [inline]
__kmalloc_cache_noprof+0x40/0x700 mm/slub.c:5766
kmalloc_noprof include/linux/slab.h:957 [inline]
iomap_fill_dirty_folios+0xf4/0x260 fs/iomap/buffered-io.c:1557
xfs_buffered_write_iomap_begin+0xa23/0x1a70 fs/xfs/xfs_iomap.c:1857
iomap_iter+0x5ef/0xeb0 fs/iomap/iter.c:110
iomap_zero_range+0x1cc/0xa30 fs/iomap/buffered-io.c:1590
xfs_zero_range+0x9a/0x100 fs/xfs/xfs_iomap.c:2289
xfs_free_file_space+0x8ad/0xcc0 fs/xfs/xfs_bmap_util.c:900
__xfs_file_fallocate+0x568/0x15f0 fs/xfs/xfs_file.c:1387
xfs_file_fallocate+0x27b/0x340 fs/xfs/xfs_file.c:1462
vfs_fallocate+0x669/0x7e0 fs/open.c:339
ksys_fallocate fs/open.c:363 [inline]
__do_sys_fallocate fs/open.c:368 [inline]
__se_sys_fallocate fs/open.c:366 [inline]
__x64_sys_fallocate+0xc0/0x110 fs/open.c:366
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fdf0878f7c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffb9feb238 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fdf089e5fa0 RCX: 00007fdf0878f7c9
RDX: 000000000000036e RSI: 0000000000000003 RDI: 0000000000000005
RBP: 00007fdf08813f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdf089e5fa0 R14: 00007fdf089e5fa0 R15: 0000000000000004
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2025-12-07 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 0:24 [syzbot] [xfs?] possible deadlock in xfs_buffered_write_iomap_begin syzbot
2025-12-07 23:10 ` syzbot [this message]
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=69360960.a70a0220.38f243.006f.GAE@google.com \
--to=syzbot+5f5f36a9ed0aadd614f3@syzkaller.appspotmail.com \
--cc=cem@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.