syzbot


BUG: looking up invalid subclass: ADDR

Status: auto-obsoleted due to no activity on 2023/02/04 17:23
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+39d19414bd6553c23c40@syzkaller.appspotmail.com
First crash: 581d, last: 560d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] BUG: looking up invalid subclass: ADDR 0 (1) 2022/09/21 06:14

Sample crash report:
loop2: detected capacity change from 0 to 4096
ntfs3: loop2: Different NTFS' sector size (1024) and media sector size (512)
BUG: looking up invalid subclass: 4294967295
turning off the locking correctness validator.
CPU: 1 PID: 17857 Comm: syz-executor.2 Not tainted 6.0.0-syzkaller-06475-g4c86114194e6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 look_up_lock_class+0xdf/0x120 kernel/locking/lockdep.c:900
 register_lock_class+0xc2/0x930 kernel/locking/lockdep.c:1287
 __lock_acquire+0xe4/0x1f60 kernel/locking/lockdep.c:4932
 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 _atomic_dec_and_lock+0x9d/0x110 lib/dec_and_lock.c:28
 iput+0x85/0x760 fs/inode.c:1765
 ntfs_fill_super+0x3af3/0x42a0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7cbc08bada
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7cbd11ff88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f7cbc08bada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f7cbd11ffe0
RBP: 00007f7cbd120020 R08: 00007f7cbd120020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f7cbd11ffe0 R15: 00000000200021c0
 </TASK>
================================================================================
UBSAN: array-index-out-of-bounds in kernel/locking/lockdep.c:1298:27
index 4294967295 is out of range for type 'struct lockdep_subclass_key [8]'
CPU: 1 PID: 17857 Comm: syz-executor.2 Not tainted 6.0.0-syzkaller-06475-g4c86114194e6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 ubsan_epilogue lib/ubsan.c:151 [inline]
 __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283
 register_lock_class+0x925/0x930 kernel/locking/lockdep.c:1298
 __lock_acquire+0xe4/0x1f60 kernel/locking/lockdep.c:4932
 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5666
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 _atomic_dec_and_lock+0x9d/0x110 lib/dec_and_lock.c:28
 iput+0x85/0x760 fs/inode.c:1765
 ntfs_fill_super+0x3af3/0x42a0 fs/ntfs3/super.c:1190
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7cbc08bada
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7cbd11ff88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f7cbc08bada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f7cbd11ffe0
RBP: 00007f7cbd120020 R08: 00007f7cbd120020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f7cbd11ffe0 R15: 00000000200021c0
 </TASK>
================================================================================

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/07 17:22 upstream 4c86114194e6 79a59635 .config console log report info ci2-upstream-fs BUG: looking up invalid subclass: ADDR
2022/10/05 22:49 upstream 2bca25eaeba6 2c6543ad .config console log report info [disk image] [vmlinux] ci2-upstream-fs BUG: looking up invalid subclass: ADDR
2022/09/25 14:06 upstream 105a36f3694e 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-upstream-fs BUG: looking up invalid subclass: ADDR
2022/09/16 22:53 upstream 6879c2d3b960 dd9a85ff .config console log report info ci-upstream-kasan-gce-smack-root BUG: looking up invalid subclass: ADDR
* Struck through repros no longer work on HEAD.