WARNING: Nested lock was not taken

0 views
Skip to first unread message

syzbot

unread,
Sep 13, 2022, 11:08:32 PM9/13/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9b4509495418 Merge tag 'for-6.0-rc4-tag' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12172f17080000
kernel config: https://syzkaller.appspot.com/x/.config?x=97276598559332bb
dashboard link: https://syzkaller.appspot.com/bug?extid=568f8994dbd80a431caf
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+568f89...@syzkaller.appspotmail.com

==================================
WARNING: Nested lock was not taken
6.0.0-rc4-syzkaller-00204-g9b4509495418 #0 Not tainted
----------------------------------
syz-executor.3/24941 is trying to lock:
ffff888038f489d8
(&s->s_inode_list_lock
){+.+.}-{2:2}
, at: spin_lock include/linux/spinlock.h:349 [inline]
, at: inode_sb_list_del fs/inode.c:503 [inline]
, at: evict+0x161/0x620 fs/inode.c:654

but this task is not holding:
general protection fault, probably for non-canonical address 0xdffffc0020000002: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x0000000100000010-0x0000000100000017]
CPU: 1 PID: 24941 Comm: syz-executor.3 Not tainted 6.0.0-rc4-syzkaller-00204-g9b4509495418 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
RIP: 0010:print_lock_nested_lock_not_held kernel/locking/lockdep.c:4885 [inline]
RIP: 0010:__lock_acquire+0x1112/0x1f60 kernel/locking/lockdep.c:5044
Code: 3c 30 00 48 8b 5c 24 70 74 12 48 89 df e8 76 e1 73 00 49 be 00 00 00 00 00 fc ff df 48 8b 1b 48 83 c3 18 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 4f e1 73 00 48 8b 33 45 31 f6 48
RSP: 0018:ffffc90008cf7828 EFLAGS: 00010003

RAX: 0000000020000002 RBX: 0000000100000017 RCX: 1359509b3d931800
RDX: ffffc9000bc7a000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffff888038c7c0e0 R08: ffffffff816d5c8d R09: ffffed1017364f14
R10: ffffed1017364f14 R11: 1ffff11017364f13 R12: ffff888038c7c348
R13: 13097edffffccc42 R14: dffffc0000000000 R15: ffff888038c7bb00
FS: 00007f9d52fb8700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f929936b1b8 CR3: 000000007a3b8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x1a7/0x400 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]
inode_sb_list_del fs/inode.c:503 [inline]
evict+0x161/0x620 fs/inode.c:654
ntfs_fill_super+0x3c6c/0x4420 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+0x2e3/0x3d0 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f9d51e8a8fa
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:00007f9d52fb7f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f9d51e8a8fa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f9d52fb7fe0
RBP: 00007f9d52fb8020 R08: 00007f9d52fb8020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f9d52fb7fe0 R15: 000000002007aa80
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:print_lock_nested_lock_not_held kernel/locking/lockdep.c:4885 [inline]
RIP: 0010:__lock_acquire+0x1112/0x1f60 kernel/locking/lockdep.c:5044
Code: 3c 30 00 48 8b 5c 24 70 74 12 48 89 df e8 76 e1 73 00 49 be 00 00 00 00 00 fc ff df 48 8b 1b 48 83 c3 18 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 4f e1 73 00 48 8b 33 45 31 f6 48
RSP: 0018:ffffc90008cf7828 EFLAGS: 00010003
RAX: 0000000020000002 RBX: 0000000100000017 RCX: 1359509b3d931800
RDX: ffffc9000bc7a000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: ffff888038c7c0e0 R08: ffffffff816d5c8d R09: ffffed1017364f14
R10: ffffed1017364f14 R11: 1ffff11017364f13 R12: ffff888038c7c348
R13: 13097edffffccc42 R14: dffffc0000000000 R15: ffff888038c7bb00
FS: 00007f9d52fb8700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f929936b1b8 CR3: 000000007a3b8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 3c 30 cmp $0x30,%al
2: 00 48 8b add %cl,-0x75(%rax)
5: 5c pop %rsp
6: 24 70 and $0x70,%al
8: 74 12 je 0x1c
a: 48 89 df mov %rbx,%rdi
d: e8 76 e1 73 00 callq 0x73e188
12: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14
19: fc ff df
1c: 48 8b 1b mov (%rbx),%rbx
1f: 48 83 c3 18 add $0x18,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 4f e1 73 00 callq 0x73e188
39: 48 8b 33 mov (%rbx),%rsi
3c: 45 31 f6 xor %r14d,%r14d
3f: 48 rex.W


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Sep 25, 2022, 9:40:29 PM9/25/22
to syzkaller-upst...@googlegroups.com
Sending this report upstream.
Reply all
Reply to author
Forward
0 new messages