* [syzbot] [block?] WARNING in null_report_zones
@ 2026-08-06 15:27 syzbot
2026-08-19 19:13 ` syzbot
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2026-08-06 15:27 UTC (permalink / raw)
To: axboe, linux-block, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 7235a3e71949 Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=15bfe3b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ccf4bea59f67007
dashboard link: https://syzkaller.appspot.com/bug?extid=67f80b67c0cfaa3bb3bb
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fd45635beaae/disk-7235a3e7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d7d2e6507223/vmlinux-7235a3e7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b5b5d8de4cea/Image-7235a3e7.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67f80b67c0cfaa3bb3bb@syzkaller.appspotmail.com
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: kernel/locking/mutex.c:625 at __mutex_lock_common kernel/locking/mutex.c:625 [inline], CPU#1: syz.1.49/5028
WARNING: kernel/locking/mutex.c:625 at __mutex_lock+0xd0c/0xf14 kernel/locking/mutex.c:821, CPU#1: syz.1.49/5028
Modules linked in:
CPU: 1 UID: 0 PID: 5028 Comm: syz.1.49 Not tainted syzkaller #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
pstate: 63400005 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : __mutex_lock_common kernel/locking/mutex.c:625 [inline]
pc : __mutex_lock+0xd0c/0xf14 kernel/locking/mutex.c:821
lr : __mutex_lock_common kernel/locking/mutex.c:625 [inline]
lr : __mutex_lock+0xd0c/0xf14 kernel/locking/mutex.c:821
sp : ffff8000974c7240
x29: ffff8000974c7390 x28: ffff8000825cb81c x27: ffff8000974c72e0
x26: 0000000000000000 x25: ffff8000974c72e8 x24: 0000000000000000
x23: ffff700012e98e58 x22: ffff8000974c7300 x21: dfff800000000000
x20: ffff8000aac2c0a8 x19: ffff8000aac2c0a8 x18: 1fffe00035bc9e28
x17: 0000000000000003 x16: ffff800088b07000 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000080000 x9 : 87bfb99deda4d800
x8 : 87bfb99deda4d800 x7 : 0000000000000000 x6 : ffff80008048e080
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff8000802f8070
x2 : 0000000100000000 x1 : ffff0000d3c78000 x0 : 0000000000000001
Call trace:
__mutex_lock_common kernel/locking/mutex.c:625 [inline] (P)
__mutex_lock+0xd0c/0xf14 kernel/locking/mutex.c:821 (P)
mutex_lock_nested+0x24/0x30 kernel/locking/mutex.c:874
null_lock_zone drivers/block/null_blk/zoned.c:39 [inline]
null_report_zones+0x298/0x878 drivers/block/null_blk/zoned.c:219
blk_revalidate_disk_zones+0x7a4/0xe64 block/blk-zoned.c:2384
null_register_zoned_dev+0xe4/0x134 drivers/block/null_blk/zoned.c:184
null_add_dev+0xeb0/0x1800 drivers/block/null_blk/main.c:2047
nullb_device_power_store+0x160/0x398 drivers/block/null_blk/main.c:501
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x27c/0x354 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x51c/0xa0c fs/read_write.c:687
ksys_write+0x12c/0x228 fs/read_write.c:739
__do_sys_write fs/read_write.c:750 [inline]
__se_sys_write fs/read_write.c:747 [inline]
__arm64_sys_write+0x84/0x98 fs/read_write.c:747
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736
el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594
irq event stamp: 131463
hardirqs last enabled at (131463): [<ffff8000803b8b90>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1673 [inline]
hardirqs last enabled at (131463): [<ffff8000803b8b90>] finish_lock_switch kernel/sched/core.c:5241 [inline]
hardirqs last enabled at (131463): [<ffff8000803b8b90>] finish_task_switch+0x234/0x858 kernel/sched/core.c:5359
hardirqs last disabled at (131462): [<ffff8000868f535c>] __schedule+0x2f8/0x2d80 kernel/sched/core.c:7087
softirqs last enabled at (124352): [<ffff80008030ff44>] softirq_handle_end kernel/softirq.c:468 [inline]
softirqs last enabled at (124352): [<ffff80008030ff44>] handle_softirqs+0xc28/0xd98 kernel/softirq.c:650
softirqs last disabled at (124285): [<ffff8000800204c0>] __do_softirq+0x14/0x20 kernel/softirq.c:656
---[ end trace 0000000000000000 ]---
Unable to handle kernel paging request at virtual address fbd529d5a0000006
KASAN: maybe wild-memory-access in range [0xdead4ead00000030-0xdead4ead00000037]
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0
[fbd529d5a0000006] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] SMP
Modules linked in:
CPU: 1 UID: 0 PID: 5028 Comm: syz.1.49 Tainted: G W syzkaller #0 PREEMPT
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : owner_on_cpu include/linux/sched.h:2323 [inline]
pc : mutex_can_spin_on_owner+0x1b0/0x300 kernel/locking/mutex.c:442
lr : instrument_atomic_read include/linux/instrumented.h:82 [inline]
lr : atomic_long_read include/linux/atomic/atomic-instrumented.h:3188 [inline]
lr : __mutex_owner kernel/locking/mutex.h:48 [inline]
lr : mutex_can_spin_on_owner+0x188/0x300 kernel/locking/mutex.c:440
sp : ffff8000974c7200
x29: ffff8000974c7200 x28: ffff8000825cb81c x27: ffff8000974c72e0
x26: 0000000000000000 x25: ffff8000974c72e8 x24: 0000000000000000
x23: ffff700012e98e58 x22: ffff8000974c7300 x21: dfff800000000000
x20: dead4ead00000034 x19: dead4ead00000000 x18: 1fffe00035bc9e28
x17: 0000000000000003 x16: ffff800088b07000 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000000
x11: 0000000000000000 x10: ffff700015585816 x9 : dfff800000000000
x8 : 1bd5a9d5a0000006 x7 : 0000000000000000 x6 : ffff8000825cb81c
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800080458ecc
x2 : 0000000000000000 x1 : 0000000000000008 x0 : 0000000000000001
Call trace:
owner_on_cpu include/linux/sched.h:2323 [inline] (P)
mutex_can_spin_on_owner+0x1b0/0x300 kernel/locking/mutex.c:442 (P)
mutex_optimistic_spin kernel/locking/mutex.c:485 [inline]
__mutex_lock_common kernel/locking/mutex.c:650 [inline]
__mutex_lock+0x188/0xf14 kernel/locking/mutex.c:821
mutex_lock_nested+0x24/0x30 kernel/locking/mutex.c:874
null_lock_zone drivers/block/null_blk/zoned.c:39 [inline]
null_report_zones+0x298/0x878 drivers/block/null_blk/zoned.c:219
blk_revalidate_disk_zones+0x7a4/0xe64 block/blk-zoned.c:2384
null_register_zoned_dev+0xe4/0x134 drivers/block/null_blk/zoned.c:184
null_add_dev+0xeb0/0x1800 drivers/block/null_blk/main.c:2047
nullb_device_power_store+0x160/0x398 drivers/block/null_blk/main.c:501
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x27c/0x354 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x51c/0xa0c fs/read_write.c:687
ksys_write+0x12c/0x228 fs/read_write.c:739
__do_sys_write fs/read_write.c:750 [inline]
__se_sys_write fs/read_write.c:747 [inline]
__arm64_sys_write+0x84/0x98 fs/read_write.c:747
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736
el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594
Code: f27df113 54000220 9100d274 d343fe88 (38f56908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f27df113 ands x19, x8, #0xfffffffffffffff8
4: 54000220 b.eq 0x48 // b.none
8: 9100d274 add x20, x19, #0x34
c: d343fe88 lsr x8, x20, #3
* 10: 38f56908 ldrsb w8, [x8, x21] <-- trapping instruction
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot] [block?] WARNING in null_report_zones
2026-08-06 15:27 [syzbot] [block?] WARNING in null_report_zones syzbot
@ 2026-08-19 19:13 ` syzbot
0 siblings, 0 replies; 2+ messages in thread
From: syzbot @ 2026-08-19 19:13 UTC (permalink / raw)
To: axboe, linux-block, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: bd5f485f3f02 Merge tag 'soc-arm-7.3' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1168219e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d6c2a05eaadaf10
dashboard link: https://syzkaller.appspot.com/bug?extid=67f80b67c0cfaa3bb3bb
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15767815580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-bd5f485f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5a13ddf1c1fa/vmlinux-bd5f485f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0dc17a20da2c/bzImage-bd5f485f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67f80b67c0cfaa3bb3bb@syzkaller.appspotmail.com
null_blk: nullb1: using native zone append
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: kernel/locking/mutex.c:625 at __mutex_lock_common kernel/locking/mutex.c:625 [inline], CPU#0: syz.0.17/5967
WARNING: kernel/locking/mutex.c:625 at __mutex_lock+0x944/0x1bc0 kernel/locking/mutex.c:821, CPU#0: syz.0.17/5967
Modules linked in:
CPU: 0 UID: 0 PID: 5967 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 04/01/2014
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:625 [inline]
RIP: 0010:__mutex_lock+0x94b/0x1bc0 kernel/locking/mutex.c:821
Code: 0f b6 14 11 38 d0 7c 08 84 d2 0f 85 b4 10 00 00 44 8b 05 08 bf 81 05 45 85 c0 75 13 48 8d 3d 5c 1d 85 05 48 c7 c6 a0 df ef 8b <67> 48 0f b9 3a 90 e9 1b f8 ff ff 4d 8d a7 f0 0a 00 00 4c 89 e7 e8
RSP: 0018:ffffc9000634f680 EFLAGS: 00010246
RAX: 0000000000000003 RBX: ffff888047c00000 RCX: 1ffffffff2284a30
RDX: 0000000000000000 RSI: ffffffff8befdfa0 RDI: ffffffff9145afe0
RBP: ffffc9000634f7f0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: dffffc0000000000 R15: ffffed100ab768d4
FS: 00007fd5599d66c0(0000) GS:ffff8880d5bd4000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000059f3c000 CR4: 0000000000352ef0
Call Trace:
<TASK>
null_lock_zone drivers/block/null_blk/zoned.c:39 [inline]
null_lock_zone drivers/block/null_blk/zoned.c:33 [inline]
null_report_zones+0x4af/0x6f0 drivers/block/null_blk/zoned.c:219
blk_revalidate_disk_zones+0x492/0xce0 block/blk-zoned.c:2384
null_add_dev+0x125f/0x1df0 drivers/block/null_blk/main.c:2047
nullb_device_power_store+0x29d/0x350 drivers/block/null_blk/main.c:501
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x302/0x4e0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x6af/0x1050 fs/read_write.c:687
ksys_write+0x12a/0x250 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd558b9e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fd5599d6028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fd558e25fa0 RCX: 00007fd558b9e0d9
RDX: 0000000000000001 RSI: 0000200000000700 RDI: 0000000000000004
RBP: 00007fd558c35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd558e26038 R14: 00007fd558e25fa0 R15: 00007fffab806348
</TASK>
----------------
Code disassembly (best guess):
0: 0f b6 14 11 movzbl (%rcx,%rdx,1),%edx
4: 38 d0 cmp %dl,%al
6: 7c 08 jl 0x10
8: 84 d2 test %dl,%dl
a: 0f 85 b4 10 00 00 jne 0x10c4
10: 44 8b 05 08 bf 81 05 mov 0x581bf08(%rip),%r8d # 0x581bf1f
17: 45 85 c0 test %r8d,%r8d
1a: 75 13 jne 0x2f
1c: 48 8d 3d 5c 1d 85 05 lea 0x5851d5c(%rip),%rdi # 0x5851d7f
23: 48 c7 c6 a0 df ef 8b mov $0xffffffff8befdfa0,%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: 90 nop
30: e9 1b f8 ff ff jmp 0xfffff850
35: 4d 8d a7 f0 0a 00 00 lea 0xaf0(%r15),%r12
3c: 4c 89 e7 mov %r12,%rdi
3f: e8 .byte 0xe8
---
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-19 19:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-06 15:27 [syzbot] [block?] WARNING in null_report_zones syzbot
2026-08-19 19:13 ` syzbot
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.