PANIC: double fault in rcu_dynticks_curr_cpu_in_eqs

7 views
Skip to first unread message

syzbot

unread,
Dec 15, 2018, 7:41:04 AM12/15/18
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 2aa55dccf83d hns3: prevent building without CONFIG_INET
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=160e4543400000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9655b05acfc97ff
dashboard link: https://syzkaller.appspot.com/bug?extid=67651c76d79784b0ff2a
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: []

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

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+67651c...@syzkaller.appspotmail.com

PANIC: double fault, error_code: 0x0
CPU: 1 PID: 435 Comm: syz-executor3 Not tainted 4.20.0-rc6+ #344
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
==================================================================
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs+0x2c/0x170 kernel/rcu/tree.c:289
Code: 89 e5 41 56 49 be 00 00 00 00 00 fc ff df 41 55 4c 8d 6d e0 41 54 49
c7 c4 40 da 02 00 53 48 8d 5d 80 48 c1 eb 03 48 83 ec 68 <48> c7 45 80 b3
8a b5 41 4a 8d 04 33 48 c7 45 88 b0 d0 11 89 48 c7
BUG: KASAN: stack-out-of-bounds in free_pgtables+0x318/0x380 mm/memory.c:389
RSP: 0018:ffff8881936d6fd8 EFLAGS: 00010296
Read of size 8 at addr ffff8881937dc250 by task syz-executor4/429

RAX: 0000000000000001 RBX: 1ffff110326dadfc RCX: ffffc9000be32000
CPU: 0 PID: 429 Comm: syz-executor4 Not tainted 4.20.0-rc6+ #344
RDX: 0000000000000000 RSI: ffffffff86bfd097 RDI: ffff8881cd29cd7c
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RBP: ffff8881936d7060 R08: ffff8881cd29c500 R09: ffffed103b5e5b5f
Call Trace:
R10: ffffed103b5e5b5f R11: ffff8881daf2dafb R12: 000000000002da40
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x244/0x39d lib/dump_stack.c:113
R13: ffff8881936d7040 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f7379d4e700(0000) GS:ffff8881daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8881936d6fc8 CR3: 0000000192fe4000 CR4: 00000000001406e0
print_address_description.cold.7+0x9/0x1ff mm/kasan/report.c:256
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kasan_report_error mm/kasan/report.c:354 [inline]
kasan_report.cold.8+0x242/0x309 mm/kasan/report.c:412
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__asan_report_load8_noabort+0x14/0x20 mm/kasan/report.c:433


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Jun 12, 2019, 6:52:04 PM6/12/19
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