BUG: unable to handle kernel paging request in wait_consider_task (2)

19 views
Skip to first unread message

syzbot

unread,
May 2, 2021, 6:57:19 PM5/2/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 7d7d1c0a Linux 4.14.232
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117d5df1d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=17ee8a0e183900d8
dashboard link: https://syzkaller.appspot.com/bug?extid=9766a9c7ec0e96585441

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

audit: type=1326 audit(1619996163.153:2744): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=2086 comm="syz-executor.2" exe="/root/syz-executor.2" sig=31 arch=c000003e syscall=202 compat=0 ip=0x4665f9 code=0x0
BUG: unable to handle kernel paging request at ffff8880004547bc
IP: wait_consider_task+0x96/0x3350 kernel/exit.c:1339
PGD c9cc067 P4D c9cc067 PUD c9cd067 PMD 10e063 PTE 0
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 31479 Comm: syz-executor.2 Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff888061a246c0 task.stack: ffff888082868000
RIP: 0010:wait_consider_task+0x96/0x3350 kernel/exit.c:1339
RSP: 0018:ffff88808286fb40 EFLAGS: 00010246
RAX: 0000000000000007 RBX: ffff888000454340 RCX: 0000000000001872
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88808286fd18
RBP: dffffc0000000000 R08: ffffffff8b99be50 R09: 000000000006008a
R10: ffff888061a24f48 R11: ffff888061a246c0 R12: ffff88808286fd18
R13: ffff888061a246c0 R14: ffff88808286fd18 R15: ffff8880004547bc
FS: 00000000032e3400(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8880004547bc CR3: 00000000471c3000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_wait_thread kernel/exit.c:1448 [inline]
do_wait+0x3e9/0x930 kernel/exit.c:1519
kernel_wait4+0x107/0x1e0 kernel/exit.c:1661
SYSC_wait4 kernel/exit.c:1673 [inline]
SyS_wait4+0xfe/0x110 kernel/exit.c:1669
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x464a97
RSP: 002b:00007ffcb7747760 EFLAGS: 00000293 ORIG_RAX: 000000000000003d
RAX: ffffffffffffffda RBX: 0000000000005731 RCX: 0000000000464a97
RDX: 0000000040000001 RSI: 00007ffcb77477fc RDI: 00000000ffffffff
RBP: 00007ffcb77477fc R08: 0000000000000000 R09: 000002d451a82cf8
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 000000000029307e R14: 0000000000000008 R15: 00007ffcb7747860
Code: 40 08 00 f3 f3 f3 e8 da b6 23 00 4c 89 f8 48 c1 e8 03 0f b6 14 28 4c 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 d1 17 00 00 <44> 8b a3 7c 04 00 00 41 83 fc 10 0f 84 a1 00 00 00 e8 a4 b6 23
RIP: wait_consider_task+0x96/0x3350 kernel/exit.c:1339 RSP: ffff88808286fb40
CR2: ffff8880004547bc
do not call blocking ops when !TASK_RUNNING; state=1 set at [<ffffffff8131a470>] do_wait+0x300/0x930 kernel/exit.c:1545
------------[ cut here ]------------
WARNING: CPU: 1 PID: 31479 at kernel/sched/core.c:5984 __might_sleep.cold+0x9f/0xb4 kernel/sched/core.c:5984


---
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,
Aug 30, 2021, 6:57:14 PM8/30/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