WARNING: locking bug in __anon_vma_prepare

5 views
Skip to first unread message

syzbot

unread,
Nov 7, 2021, 10:44:20 PM11/7/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ce840177930f Merge tag 'defconfig-5.16' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=176caba6b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=647adc5a101c9bf3
dashboard link: https://syzkaller.appspot.com/bug?extid=156df0e842fba1cbd697
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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+156df0...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 19684 at kernel/locking/lockdep.c:897 look_up_lock_class+0x6a/0xd0 kernel/locking/lockdep.c:897
Modules linked in:
CPU: 0 PID: 19684 Comm: modprobe Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:look_up_lock_class+0x6a/0xd0 kernel/locking/lockdep.c:897
Code: 85 c0 75 0a eb 57 48 8b 00 48 85 c0 74 4f 48 39 70 40 75 f2 48 8b 4f 18 48 39 88 b0 00 00 00 74 0b 48 81 3f 20 f5 f3 8e 74 02 <0f> 0b 5d c3 9c 5a 80 e6 02 74 c2 e8 36 0b 9e fa 85 c0 74 1f 8b 05
RSP: 0000:ffffc9000430f910 EFLAGS: 00010002
RAX: ffffffff8fd54660 RBX: ffffffff902899c0 RCX: 0000000000000000
RDX: 0000000000000046 RSI: ffffffff9029c460 RDI: ffff888000112d78
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888000112d78
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb58eb5b028 CR3: 0000000074f50000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000600
Call Trace:
<TASK>
register_lock_class+0xb7/0x10c0 kernel/locking/lockdep.c:1246
__lock_acquire+0x105/0x54a0 kernel/locking/lockdep.c:4894
lock_acquire kernel/locking/lockdep.c:5625 [inline]
lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590
down_write+0x90/0x150 kernel/locking/rwsem.c:1527
anon_vma_lock_write include/linux/rmap.h:116 [inline]
__anon_vma_prepare+0xbd/0x560 mm/rmap.c:204
anon_vma_prepare include/linux/rmap.h:149 [inline]
do_anonymous_page mm/memory.c:3767 [inline]
handle_pte_fault mm/memory.c:4568 [inline]
__handle_mm_fault+0x3c58/0x5280 mm/memory.c:4705
handle_mm_fault+0x1c8/0x790 mm/memory.c:4803
do_user_addr_fault+0x489/0x11c0 arch/x86/mm/fault.c:1397
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x9e/0x180 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x7fb58e94822f
Code: 00 00 48 89 54 24 10 4c 89 54 24 08 e8 5a 58 ff ff 48 85 c0 49 89 c6 0f 84 d5 01 00 00 4c 8b 54 24 08 48 8b 54 24 10 4c 89 e6 <49> 89 46 28 4e 8d 94 10 70 04 00 00 4c 89 90 c8 02 00 00 49 8d 7a
RSP: 002b:00007ffe00df8330 EFLAGS: 00010206
RAX: 00007fb58eb5b000 RBX: 0000000000000009 RCX: 00007fb58e95630a
RDX: 000000000000000a RSI: 00005627aa200c81 RDI: 00007fb58eb5b000
RBP: 0000000000000000 R08: ffffffffffffffff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00005627aa200c81
R13: 00007fb58eb62170 R14: 00007fb58eb5b000 R15: 0000000000000000
</TASK>


---
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,
Feb 1, 2022, 10:38:13 PM2/1/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages