general protection fault in rcu_process_callbacks

11 views
Skip to first unread message

syzbot

unread,
Jun 3, 2021, 9:59:21 AM6/3/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1722257b Linux 4.19.193
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13df8e0bd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd6b8809ec913bf1
dashboard link: https://syzkaller.appspot.com/bug?extid=b7681fda8ae1d0ba356d

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

device lo entered promiscuous mode
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 18 Comm: ksoftirqd/1 Not tainted 4.19.193-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:lookup_object lib/debugobjects.c:156 [inline]
RIP: 0010:debug_object_active_state lib/debugobjects.c:727 [inline]
RIP: 0010:debug_object_active_state+0x14b/0x330 lib/debugobjects.c:713
Code: 8f 01 00 00 48 8b ab 80 bb 36 8d 31 db 48 85 ed 74 44 49 bc 00 00 00 00 00 fc ff df 48 8d 7d 18 83 c3 01 48 89 f8 48 c1 e8 03 <42> 80 3c 20 00 0f 85 03 01 00 00 4c 3b 7d 18 74 71 48 89 e8 48 c1
RSP: 0018:ffff8880b5ad7bf0 EFLAGS: 00010006
RAX: 00000000e0e00003 RBX: 0000000000000002 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff89f85dc0 RDI: 0000000707000018
RBP: 0000000707000000 R08: 0000000000000282 R09: fffffbfff1a82fe1
R10: ffffffff8d417f0b R11: 0000000000000000 R12: dffffc0000000000
R13: 1ffff11016b5af82 R14: ffffffff8d417f08 R15: ffff88803fdc5f10
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564154f4d160 CR3: 0000000009e6d000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
debug_rcu_head_unqueue kernel/rcu/rcu.h:202 [inline]
rcu_do_batch kernel/rcu/tree.c:2583 [inline]
invoke_rcu_callbacks kernel/rcu/tree.c:2897 [inline]
__rcu_process_callbacks kernel/rcu/tree.c:2864 [inline]
rcu_process_callbacks+0x9af/0x18b0 kernel/rcu/tree.c:2881
__do_softirq+0x265/0x980 kernel/softirq.c:292
run_ksoftirqd+0x57/0x110 kernel/softirq.c:653
smpboot_thread_fn+0x655/0x9e0 kernel/smpboot.c:164
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:

======================================================


---
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,
Oct 1, 2021, 9:59:12 AM10/1/21
to syzkaller...@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