BUG: soft lockup in select_collect
12 views
Skip to first unread message
syzbot
May 18, 2018, 7:25:05 PM5/18/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 82f9e2d5dba6 Merge branch 'bpf-af-xdp-cleanups'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=100d2177800000
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboard link: https://syzkaller.appspot.com/bug?extid=c4f884d0dbcaf25336a4
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org
vi...@zeniv.linux.org.uk]
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+c4f884...@syzkaller.appspotmail.com
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [syz-executor2:4564]
Modules linked in:
irq event stamp: 19858060
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
seqcount_lockdep_reader_access include/linux/seqlock.h:83 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
read_seqcount_begin include/linux/seqlock.h:164 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>] read_seqbegin
include/linux/seqlock.h:433 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
read_seqbegin_or_lock include/linux/seqlock.h:529 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
d_walk+0x80f/0xc80 fs/dcache.c:1248
hardirqs last disabled at (19858060): [<ffffffff87800905>]
interrupt_entry+0xb5/0xf0 arch/x86/entry/entry_64.S:625
softirqs last enabled at (6290066): [<ffffffff87a00778>]
__do_softirq+0x778/0xaf5 kernel/softirq.c:311
softirqs last disabled at (6290001): [<ffffffff81475241>] invoke_softirq
kernel/softirq.c:365 [inline]
softirqs last disabled at (6290001): [<ffffffff81475241>]
irq_exit+0x1d1/0x200 kernel/softirq.c:405
CPU: 0 PID: 4564 Comm: syz-executor2 Not tainted 4.17.0-rc4+ #14
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__write_once_size include/linux/compiler.h:215 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4b/0x50 kernel/kcov.c:109
RSP: 0018:ffff88019f63f8f8 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff88019f630600 RBX: 1ffff10033ec7f24 RCX: ffffffff81c5f164
RDX: 0000000000000000 RSI: ffffffff81c5f1f5 RDI: ffff88019f63fc28
RBP: ffff88019f63f8f8 R08: ffff88019f630600 R09: ffffed0039c5a678
R10: ffffed0039c5a678 R11: ffff8801ce2d33c3 R12: ffff88019f63fc10
R13: ffff8801ce2d3340 R14: ffff88019f63fc18 R15: ffff88019f63f9c0
FS: 00000000013d9940(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000013e2978 CR3: 000000019f601000 CR4: 00000000001406f0
DR0: 0000000020000000 DR1: 00000000200001c0 DR2: 00000000200001c0
DR3: 00000000200001c0 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
list_empty include/linux/list.h:203 [inline]
select_collect+0x175/0x5f0 fs/dcache.c:1465
d_walk+0x3c3/0xc80 fs/dcache.c:1276
shrink_dcache_parent+0x179/0x230 fs/dcache.c:1486
vfs_rmdir+0x202/0x470 fs/namei.c:3850
do_rmdir+0x523/0x610 fs/namei.c:3911
__do_sys_rmdir fs/namei.c:3929 [inline]
__se_sys_rmdir fs/namei.c:3927 [inline]
__x64_sys_rmdir+0x36/0x40 fs/namei.c:3927
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455777
RSP: 002b:00007ffd850cadb8 EFLAGS: 00000206 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 0000000000455777
RDX: 0000000000000000 RSI: 00007ffd850ccb60 RDI: 00007ffd850ccb60
RBP: 00007ffd850ccb60 R08: 0000000000000000 R09: 0000000000000001
R10: 000000000000000a R11: 0000000000000206 R12: 00000000013da940
R13: 0000000000000000 R14: 0000000000000d2d R15: 0000000000085ec4
Code: 8b 90 78 12 00 00 83 fa 02 75 20 48 8b 88 80 12 00 00 8b 80 7c 12 00
00 48 8b 11 48 83 c2 01 48 39 d0 76 07 48 89 34 d1 48 89 11 <5d> c3 0f 1f
00 55 40 0f b6 d6 40 0f b6 f7 31 ff 48 89 e5 48 8b
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4568 Comm: syz-executor5 Not tainted 4.17.0-rc4+ #14
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:list_empty include/linux/list.h:203 [inline]
RIP: 0010:select_collect+0x1d7/0x5f0 fs/dcache.c:1465
RSP: 0018:ffff88019d43f908 EFLAGS: 00000a06
RAX: dffffc0000000000 RBX: 1ffff10033a87f24 RCX: ffffffff81c5f164
RDX: 1ffff10033a87f28 RSI: ffffffff81c5f1f5 RDI: ffff88019d43fc28
RBP: ffff88019d43f9e8 R08: ffff88019d436700 R09: ffffed003932bfd0
R10: ffffed003932bfd0 R11: ffff8801c995fe83 R12: ffff88019d43fc18
R13: 1ffff10033a87f28 R14: ffff88019d43fc18 R15: dffffc0000000000
FS: 0000000002091940(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000209a978 CR3: 000000019d417000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
d_walk+0x3c3/0xc80 fs/dcache.c:1276
shrink_dcache_parent+0x179/0x230 fs/dcache.c:1486
vfs_rmdir+0x202/0x470 fs/namei.c:3850
do_rmdir+0x523/0x610 fs/namei.c:3911
__do_sys_rmdir fs/namei.c:3929 [inline]
__se_sys_rmdir fs/namei.c:3927 [inline]
__x64_sys_rmdir+0x36/0x40 fs/namei.c:3927
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455777
RSP: 002b:00007ffe4dd62ea8 EFLAGS: 00000202 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 0000000000455777
RDX: 0000000000000000 RSI: 00007ffe4dd64c50 RDI: 00007ffe4dd64c50
RBP: 00007ffe4dd64c50 R08: 0000000000000000 R09: 0000000000000001
R10: 000000000000000a R11: 0000000000000202 R12: 0000000002092940
R13: 0000000000000000 R14: 0000000000000db9 R15: 0000000000085ec5
Code: 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 15 03 00 00 4d 89 67 80
49 c1 ed 03 49 bf 00 00 00 00 00 fc ff df 43 c6 44 3d 00 f8 <4d> 39 e6 0f
84 b8 00 00 00 e8 2b 3b b3 ff 65 4c 8b 24 25 c0 ed
---
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 found the following crash on:
HEAD commit: 82f9e2d5dba6 Merge branch 'bpf-af-xdp-cleanups'
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=100d2177800000
kernel config: https://syzkaller.appspot.com/x/.config?x=b632d8e2c2ab2c1
dashboard link: https://syzkaller.appspot.com/bug?extid=c4f884d0dbcaf25336a4
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org
vi...@zeniv.linux.org.uk]
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+c4f884...@syzkaller.appspotmail.com
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [syz-executor2:4564]
Modules linked in:
irq event stamp: 19858060
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
seqcount_lockdep_reader_access include/linux/seqlock.h:83 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
read_seqcount_begin include/linux/seqlock.h:164 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>] read_seqbegin
include/linux/seqlock.h:433 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
read_seqbegin_or_lock include/linux/seqlock.h:529 [inline]
hardirqs last enabled at (19858059): [<ffffffff81c6992f>]
d_walk+0x80f/0xc80 fs/dcache.c:1248
hardirqs last disabled at (19858060): [<ffffffff87800905>]
interrupt_entry+0xb5/0xf0 arch/x86/entry/entry_64.S:625
softirqs last enabled at (6290066): [<ffffffff87a00778>]
__do_softirq+0x778/0xaf5 kernel/softirq.c:311
softirqs last disabled at (6290001): [<ffffffff81475241>] invoke_softirq
kernel/softirq.c:365 [inline]
softirqs last disabled at (6290001): [<ffffffff81475241>]
irq_exit+0x1d1/0x200 kernel/softirq.c:405
CPU: 0 PID: 4564 Comm: syz-executor2 Not tainted 4.17.0-rc4+ #14
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__write_once_size include/linux/compiler.h:215 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4b/0x50 kernel/kcov.c:109
RSP: 0018:ffff88019f63f8f8 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13
RAX: ffff88019f630600 RBX: 1ffff10033ec7f24 RCX: ffffffff81c5f164
RDX: 0000000000000000 RSI: ffffffff81c5f1f5 RDI: ffff88019f63fc28
RBP: ffff88019f63f8f8 R08: ffff88019f630600 R09: ffffed0039c5a678
R10: ffffed0039c5a678 R11: ffff8801ce2d33c3 R12: ffff88019f63fc10
R13: ffff8801ce2d3340 R14: ffff88019f63fc18 R15: ffff88019f63f9c0
FS: 00000000013d9940(0000) GS:ffff8801dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000013e2978 CR3: 000000019f601000 CR4: 00000000001406f0
DR0: 0000000020000000 DR1: 00000000200001c0 DR2: 00000000200001c0
DR3: 00000000200001c0 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
list_empty include/linux/list.h:203 [inline]
select_collect+0x175/0x5f0 fs/dcache.c:1465
d_walk+0x3c3/0xc80 fs/dcache.c:1276
shrink_dcache_parent+0x179/0x230 fs/dcache.c:1486
vfs_rmdir+0x202/0x470 fs/namei.c:3850
do_rmdir+0x523/0x610 fs/namei.c:3911
__do_sys_rmdir fs/namei.c:3929 [inline]
__se_sys_rmdir fs/namei.c:3927 [inline]
__x64_sys_rmdir+0x36/0x40 fs/namei.c:3927
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455777
RSP: 002b:00007ffd850cadb8 EFLAGS: 00000206 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 0000000000455777
RDX: 0000000000000000 RSI: 00007ffd850ccb60 RDI: 00007ffd850ccb60
RBP: 00007ffd850ccb60 R08: 0000000000000000 R09: 0000000000000001
R10: 000000000000000a R11: 0000000000000206 R12: 00000000013da940
R13: 0000000000000000 R14: 0000000000000d2d R15: 0000000000085ec4
Code: 8b 90 78 12 00 00 83 fa 02 75 20 48 8b 88 80 12 00 00 8b 80 7c 12 00
00 48 8b 11 48 83 c2 01 48 39 d0 76 07 48 89 34 d1 48 89 11 <5d> c3 0f 1f
00 55 40 0f b6 d6 40 0f b6 f7 31 ff 48 89 e5 48 8b
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4568 Comm: syz-executor5 Not tainted 4.17.0-rc4+ #14
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:list_empty include/linux/list.h:203 [inline]
RIP: 0010:select_collect+0x1d7/0x5f0 fs/dcache.c:1465
RSP: 0018:ffff88019d43f908 EFLAGS: 00000a06
RAX: dffffc0000000000 RBX: 1ffff10033a87f24 RCX: ffffffff81c5f164
RDX: 1ffff10033a87f28 RSI: ffffffff81c5f1f5 RDI: ffff88019d43fc28
RBP: ffff88019d43f9e8 R08: ffff88019d436700 R09: ffffed003932bfd0
R10: ffffed003932bfd0 R11: ffff8801c995fe83 R12: ffff88019d43fc18
R13: 1ffff10033a87f28 R14: ffff88019d43fc18 R15: dffffc0000000000
FS: 0000000002091940(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000209a978 CR3: 000000019d417000 CR4: 00000000001406e0
DR0: 0000000020000000 DR1: 0000000020000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
d_walk+0x3c3/0xc80 fs/dcache.c:1276
shrink_dcache_parent+0x179/0x230 fs/dcache.c:1486
vfs_rmdir+0x202/0x470 fs/namei.c:3850
do_rmdir+0x523/0x610 fs/namei.c:3911
__do_sys_rmdir fs/namei.c:3929 [inline]
__se_sys_rmdir fs/namei.c:3927 [inline]
__x64_sys_rmdir+0x36/0x40 fs/namei.c:3927
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455777
RSP: 002b:00007ffe4dd62ea8 EFLAGS: 00000202 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 0000000000455777
RDX: 0000000000000000 RSI: 00007ffe4dd64c50 RDI: 00007ffe4dd64c50
RBP: 00007ffe4dd64c50 R08: 0000000000000000 R09: 0000000000000001
R10: 000000000000000a R11: 0000000000000202 R12: 0000000002092940
R13: 0000000000000000 R14: 0000000000000db9 R15: 0000000000085ec5
Code: 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 15 03 00 00 4d 89 67 80
49 c1 ed 03 49 bf 00 00 00 00 00 fc ff df 43 c6 44 3d 00 f8 <4d> 39 e6 0f
84 b8 00 00 00 e8 2b 3b b3 ff 65 4c 8b 24 25 c0 ed
---
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
May 19, 2018, 5:35:43 AM5/19/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
False positive due to too low watchdog_thresh setting. Fixed now.
#syz invalid
> --
> 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/000000000000019e72056c8343f1%40google.com.
> For more options, visit https://groups.google.com/d/optout.
#syz invalid
> 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/000000000000019e72056c8343f1%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages