general protection fault in __call_rcu_common
4 views
Skip to first unread message
syzbot
Feb 8, 2023, 10:51:45 PM2/8/23
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 4fafd96910ad Add linux-next specific files for 20230203
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13bc5c19480000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d2fba7d42502ca4
dashboard link: https://syzkaller.appspot.com/bug?extid=d30a352ae4ceab99e10a
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/348cc2da441a/disk-4fafd969.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e2dedc500f12/vmlinux-4fafd969.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fae710d9ebd8/bzImage-4fafd969.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d30a35...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc000000800a: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x0000000000040050-0x0000000000040057]
CPU: 0 PID: 10108 Comm: syz-executor.2 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__hlist_del include/linux/list.h:901 [inline]
RIP: 0010:hlist_del include/linux/list.h:913 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:213 [inline]
RIP: 0010:alloc_object lib/debugobjects.c:230 [inline]
RIP: 0010:__debug_object_init+0x21f/0xf10 lib/debugobjects.c:577
Code: c1 ef 03 80 3c 37 00 0f 85 34 0a 00 00 48 85 c0 48 89 01 74 24 48 8d 78 08 48 be 00 00 00 00 00 fc ff df 49 89 fa 49 c1 ea 03 <41> 80 3c 32 00 0f 85 e4 09 00 00 48 89 48 08 48 b8 00 01 00 00 00
RSP: 0018:ffffc9001619f878 EFLAGS: 00010006
RAX: 0000000000040048 RBX: 00000000000aede0 RCX: ffff8880b9838c00
RDX: ffff8880b9838c00 RSI: dffffc0000000000 RDI: 0000000000040050
RBP: ffff88808844b930 R08: 0000000000000001 R09: 0000000000000003
R10: 000000000000800a R11: 0000000000000000 R12: 1ffff92002c33f1d
R13: ffff88802b8b4480 R14: ffffffff91eef828 R15: ffffffff91eef820
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa18d1a8000 CR3: 000000002a22b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_object_init lib/debugobjects.c:624 [inline]
debug_object_activate+0x330/0x3e0 lib/debugobjects.c:710
debug_rcu_head_queue kernel/rcu/rcu.h:226 [inline]
__call_rcu_common.constprop.0+0x2c/0x7d0 kernel/rcu/tree.c:2610
__change_pid+0x1c1/0x2d0 kernel/pid.c:353
__unhash_process kernel/exit.c:125 [inline]
__exit_signal kernel/exit.c:198 [inline]
release_task+0x9e3/0x1870 kernel/exit.c:255
exit_notify kernel/exit.c:761 [inline]
do_exit+0x1516/0x2b60 kernel/exit.c:889
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
get_signal+0x2321/0x25b0 kernel/signal.c:2859
arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:301
RIP: 0033:0x7fc0a7c8d4f1
Code: Unable to access opcode bytes at 0x7fc0a7c8d4c7.
RSP: 002b:00007fc0a897f2f0 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 00007fc0a897f700 RCX: 00007fc0a7c8d4f1
RDX: 00007fc0a897f9d0 RSI: 00007fc0a897f2f0 RDI: 00000000003d0f00
RBP: 00007ffe355e4ce0 R08: 00007fc0a897f700 R09: 00007fc0a897f700
R10: 00007fc0a897f9d0 R11: 0000000000000206 R12: 00007ffe355e4b4e
R13: 00007ffe355e4b4f R14: 00007fc0a897f300 R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__hlist_del include/linux/list.h:901 [inline]
RIP: 0010:hlist_del include/linux/list.h:913 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:213 [inline]
RIP: 0010:alloc_object lib/debugobjects.c:230 [inline]
RIP: 0010:__debug_object_init+0x21f/0xf10 lib/debugobjects.c:577
Code: c1 ef 03 80 3c 37 00 0f 85 34 0a 00 00 48 85 c0 48 89 01 74 24 48 8d 78 08 48 be 00 00 00 00 00 fc ff df 49 89 fa 49 c1 ea 03 <41> 80 3c 32 00 0f 85 e4 09 00 00 48 89 48 08 48 b8 00 01 00 00 00
RSP: 0018:ffffc9001619f878 EFLAGS: 00010006
RAX: 0000000000040048 RBX: 00000000000aede0 RCX: ffff8880b9838c00
RDX: ffff8880b9838c00 RSI: dffffc0000000000 RDI: 0000000000040050
RBP: ffff88808844b930 R08: 0000000000000001 R09: 0000000000000003
R10: 000000000000800a R11: 0000000000000000 R12: 1ffff92002c33f1d
R13: ffff88802b8b4480 R14: ffffffff91eef828 R15: ffffffff91eef820
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa18d1a8000 CR3: 000000002a22b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: c1 ef 03 shr $0x3,%edi
3: 80 3c 37 00 cmpb $0x0,(%rdi,%rsi,1)
7: 0f 85 34 0a 00 00 jne 0xa41
d: 48 85 c0 test %rax,%rax
10: 48 89 01 mov %rax,(%rcx)
13: 74 24 je 0x39
15: 48 8d 78 08 lea 0x8(%rax),%rdi
19: 48 be 00 00 00 00 00 movabs $0xdffffc0000000000,%rsi
20: fc ff df
23: 49 89 fa mov %rdi,%r10
26: 49 c1 ea 03 shr $0x3,%r10
* 2a: 41 80 3c 32 00 cmpb $0x0,(%r10,%rsi,1) <-- trapping instruction
2f: 0f 85 e4 09 00 00 jne 0xa19
35: 48 89 48 08 mov %rcx,0x8(%rax)
39: 48 rex.W
3a: b8 00 01 00 00 mov $0x100,%eax
---
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 found the following issue on:
HEAD commit: 4fafd96910ad Add linux-next specific files for 20230203
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13bc5c19480000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d2fba7d42502ca4
dashboard link: https://syzkaller.appspot.com/bug?extid=d30a352ae4ceab99e10a
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/348cc2da441a/disk-4fafd969.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e2dedc500f12/vmlinux-4fafd969.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fae710d9ebd8/bzImage-4fafd969.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d30a35...@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc000000800a: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x0000000000040050-0x0000000000040057]
CPU: 0 PID: 10108 Comm: syz-executor.2 Not tainted 6.2.0-rc6-next-20230203-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:__hlist_del include/linux/list.h:901 [inline]
RIP: 0010:hlist_del include/linux/list.h:913 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:213 [inline]
RIP: 0010:alloc_object lib/debugobjects.c:230 [inline]
RIP: 0010:__debug_object_init+0x21f/0xf10 lib/debugobjects.c:577
Code: c1 ef 03 80 3c 37 00 0f 85 34 0a 00 00 48 85 c0 48 89 01 74 24 48 8d 78 08 48 be 00 00 00 00 00 fc ff df 49 89 fa 49 c1 ea 03 <41> 80 3c 32 00 0f 85 e4 09 00 00 48 89 48 08 48 b8 00 01 00 00 00
RSP: 0018:ffffc9001619f878 EFLAGS: 00010006
RAX: 0000000000040048 RBX: 00000000000aede0 RCX: ffff8880b9838c00
RDX: ffff8880b9838c00 RSI: dffffc0000000000 RDI: 0000000000040050
RBP: ffff88808844b930 R08: 0000000000000001 R09: 0000000000000003
R10: 000000000000800a R11: 0000000000000000 R12: 1ffff92002c33f1d
R13: ffff88802b8b4480 R14: ffffffff91eef828 R15: ffffffff91eef820
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa18d1a8000 CR3: 000000002a22b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debug_object_init lib/debugobjects.c:624 [inline]
debug_object_activate+0x330/0x3e0 lib/debugobjects.c:710
debug_rcu_head_queue kernel/rcu/rcu.h:226 [inline]
__call_rcu_common.constprop.0+0x2c/0x7d0 kernel/rcu/tree.c:2610
__change_pid+0x1c1/0x2d0 kernel/pid.c:353
__unhash_process kernel/exit.c:125 [inline]
__exit_signal kernel/exit.c:198 [inline]
release_task+0x9e3/0x1870 kernel/exit.c:255
exit_notify kernel/exit.c:761 [inline]
do_exit+0x1516/0x2b60 kernel/exit.c:889
do_group_exit+0xd4/0x2a0 kernel/exit.c:1019
get_signal+0x2321/0x25b0 kernel/signal.c:2859
arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:301
RIP: 0033:0x7fc0a7c8d4f1
Code: Unable to access opcode bytes at 0x7fc0a7c8d4c7.
RSP: 002b:00007fc0a897f2f0 EFLAGS: 00000206 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 00007fc0a897f700 RCX: 00007fc0a7c8d4f1
RDX: 00007fc0a897f9d0 RSI: 00007fc0a897f2f0 RDI: 00000000003d0f00
RBP: 00007ffe355e4ce0 R08: 00007fc0a897f700 R09: 00007fc0a897f700
R10: 00007fc0a897f9d0 R11: 0000000000000206 R12: 00007ffe355e4b4e
R13: 00007ffe355e4b4f R14: 00007fc0a897f300 R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__hlist_del include/linux/list.h:901 [inline]
RIP: 0010:hlist_del include/linux/list.h:913 [inline]
RIP: 0010:__alloc_object lib/debugobjects.c:213 [inline]
RIP: 0010:alloc_object lib/debugobjects.c:230 [inline]
RIP: 0010:__debug_object_init+0x21f/0xf10 lib/debugobjects.c:577
Code: c1 ef 03 80 3c 37 00 0f 85 34 0a 00 00 48 85 c0 48 89 01 74 24 48 8d 78 08 48 be 00 00 00 00 00 fc ff df 49 89 fa 49 c1 ea 03 <41> 80 3c 32 00 0f 85 e4 09 00 00 48 89 48 08 48 b8 00 01 00 00 00
RSP: 0018:ffffc9001619f878 EFLAGS: 00010006
RAX: 0000000000040048 RBX: 00000000000aede0 RCX: ffff8880b9838c00
RDX: ffff8880b9838c00 RSI: dffffc0000000000 RDI: 0000000000040050
RBP: ffff88808844b930 R08: 0000000000000001 R09: 0000000000000003
R10: 000000000000800a R11: 0000000000000000 R12: 1ffff92002c33f1d
R13: ffff88802b8b4480 R14: ffffffff91eef828 R15: ffffffff91eef820
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa18d1a8000 CR3: 000000002a22b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: c1 ef 03 shr $0x3,%edi
3: 80 3c 37 00 cmpb $0x0,(%rdi,%rsi,1)
7: 0f 85 34 0a 00 00 jne 0xa41
d: 48 85 c0 test %rax,%rax
10: 48 89 01 mov %rax,(%rcx)
13: 74 24 je 0x39
15: 48 8d 78 08 lea 0x8(%rax),%rdi
19: 48 be 00 00 00 00 00 movabs $0xdffffc0000000000,%rsi
20: fc ff df
23: 49 89 fa mov %rdi,%r10
26: 49 c1 ea 03 shr $0x3,%r10
* 2a: 41 80 3c 32 00 cmpb $0x0,(%r10,%rsi,1) <-- trapping instruction
2f: 0f 85 e4 09 00 00 jne 0xa19
35: 48 89 48 08 mov %rcx,0x8(%rax)
39: 48 rex.W
3a: b8 00 01 00 00 mov $0x100,%eax
---
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
Sep 8, 2023, 12:59:39 AM9/8/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages