general protection fault in cpuacct_charge (2)

5 views
Skip to first unread message

syzbot

unread,
Jan 15, 2019, 11:53:05 AM1/15/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 3719876809e7 sbitmap: Protect swap_lock from softirqs
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14bbd417400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8a4dffabfb4e36f9
dashboard link: https://syzkaller.appspot.com/bug?extid=e9651a3e731d6710fd82
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [linux-...@vger.kernel.org tg...@linutronix.de]

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

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: 64 Comm: ksoftirq�%1 Not tainted 5.0.0-rc2+ #26
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:task_css include/linux/cgroup.h:479 [inline]
RIP: 0010:task_ca kernel/sched/cpuacct.c:43 [inline]
RIP: 0010:cpuacct_charge+0x19a/0x440 kernel/sched/cpuacct.c:349
Code: ac 8a 08 00 85 c0 74 0d 80 3d 92 5e f5 08 00 0f 84 99 01 00 00 49 8d
7e 10 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f
85 42 02 00 00 4d 8b 66 10 4d 85 e4 0f 84 a5 00 00
RSP: 0018:ffff8880ae707560 EFLAGS: 00010002
RAX: dffffc0000000000 RBX: ffff8880a94ca440 RCX: 1ffffffff14b7b97
RDX: 0000000000000002 RSI: 00000000ffff8880 RDI: 0000000000000010
RBP: ffff8880ae7075f8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880ae707520 R12: dffffc0000000000
R13: 4dc81feac6e948e1 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000068 CR3: 0000000092a4a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
cgroup_account_cputime include/linux/cgroup.h:762 [inline]
update_curr+0x371/0xbc0 kernel/sched/fair.c:830
enqueue_entity+0x3e5/0x20b0 kernel/sched/fair.c:3880
enqueue_task_fair+0x237/0x10c0 kernel/sched/fair.c:5133
enqueue_task kernel/sched/core.c:730 [inline]
activate_task+0x11d/0x470 kernel/sched/core.c:751
ttwu_activate kernel/sched/core.c:1643 [inline]
ttwu_do_activate+0xd4/0x1f0 kernel/sched/core.c:1702
ttwu_queue kernel/sched/core.c:1847 [inline]
try_to_wake_up+0x997/0x1480 kernel/sched/core.c:2057
wake_up_process+0x10/0x20 kernel/sched/core.c:2129
hrtimer_wakeup+0x48/0x60 kernel/time/hrtimer.c:1637
__run_hrtimer kernel/time/hrtimer.c:1389 [inline]
__hrtimer_run_queues+0x3a7/0x1050 kernel/time/hrtimer.c:1451
hrtimer_interrupt+0x314/0x770 kernel/time/hrtimer.c:1509
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1035 [inline]
smp_apic_timer_interrupt+0x18d/0x760 arch/x86/kernel/apic/apic.c:1060
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:807
</IRQ>
Modules linked in:
---[ end trace baebb919e60cf735 ]---
RIP: 0010:task_css include/linux/cgroup.h:479 [inline]
RIP: 0010:task_ca kernel/sched/cpuacct.c:43 [inline]
RIP: 0010:cpuacct_charge+0x19a/0x440 kernel/sched/cpuacct.c:349
Code: ac 8a 08 00 85 c0 74 0d 80 3d 92 5e f5 08 00 0f 84 99 01 00 00 49 8d
7e 10 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f
85 42 02 00 00 4d 8b 66 10 4d 85 e4 0f 84 a5 00 00
RSP: 0018:ffff8880ae707560 EFLAGS: 00010002
RAX: dffffc0000000000 RBX: ffff8880a94ca440 RCX: 1ffffffff14b7b97
RDX: 0000000000000002 RSI: 00000000ffff8880 RDI: 0000000000000010
RBP: ffff8880ae7075f8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880ae707520 R12: dffffc0000000000
R13: 4dc81feac6e948e1 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000068 CR3: 0000000092a4a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

Dmitry Vyukov

unread,
Jan 15, 2019, 11:59:44 AM1/15/19
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
#syz dup: kernel panic: stack is corrupted in udp4_lib_lookup2
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/000000000000b01c45057f81fe8e%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages