BUG: unable to handle kernel paging request in SyS_pselect6

10 views
Skip to first unread message

syzbot

unread,
Dec 4, 2017, 1:22:03 AM12/4/17
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
4131d5166185d0d75b5f1d4bf362a9e0bac05598
git://git.cmpxchg.org/linux-mmots.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.

Unfortunately, I don't have any reproducer for this bug yet.
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org
vi...@zeniv.linux.org.uk]

QAT: Invalid ioctl
QAT: Invalid ioctl
BUG: unable to handle kernel paging request at 000000000afe707b
IP: SYSC_pselect6 fs/select.c:764 [inline]
IP: SyS_pselect6+0x128/0x650 fs/select.c:755
PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 8116 Comm: syz-executor0 Not tainted 4.15.0-rc1-mm1+ #29
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
task: 000000001b7d7974 task.stack: 00000000e7757ffd
RIP: 0010:SYSC_pselect6 fs/select.c:764 [inline]
RIP: 0010:SyS_pselect6+0x128/0x650 fs/select.c:755
RSP: 0018:ffff8801c69bfdc0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 1ffff10038d37fc0 RCX: ffffffff81b44baf
RDX: 0000000000000004 RSI: ffffc900017c6000 RDI: ffff8801ced51620
RBP: ffff8801c69bff48 R08: 0000000020000000 R09: 0000000020000000
R10: 0000000020000000 R11: ffff8801ced50080 R12: ffff8801c69bff20
R13: 0000000020000000 R14: 0000000080000081 R15: 0000000020000000
FS: 00007f0559557700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 00000001c8fb1000 CR4: 00000000001426e0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff1 DR7: 00000000000b0602
Call Trace:
entry_SYSCALL_64_fastpath+0x1f/0x96
RIP: 0033:0x4529d9
RSP: 002b:00007f0559556c58 EFLAGS: 00000212 ORIG_RAX: 000000000000010e
RAX: ffffffffffffffda RBX: 0000000000758020 RCX: 00000000004529d9
RDX: 0000000020000000 RSI: 0000000020001000 RDI: 0000000000000040
RBP: 00000000000003e0 R08: 0000000020000000 R09: 0000000020000000
R10: 0000000020000000 R11: 0000000000000212 R12: 00000000006f2da0
R13: 00000000ffffffff R14: 00007f05595576d4 R15: 0000000000000000
Code: 3c 02 00 0f 85 1c 05 00 00 49 8b 86 a0 15 00 00 48 83 e8 10 49 39 c5
0f 87 b4 03 00 00 e8 01 f0 bb ff 0f 1f 00 31 c0 4d 8b 75 00 <0f> 1f 00 85
c0 89 85 b0 fe ff ff 0f 85 95 03 00 00 e8 e2 ef bb
RIP: SYSC_pselect6 fs/select.c:764 [inline] RSP: ffff8801c69bfdc0
RIP: SyS_pselect6+0x128/0x650 fs/select.c:755 RSP: ffff8801c69bfdc0
CR2: fffffffffffffff8
---[ end trace a13b802008844579 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is committed, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log

Dmitry Vyukov

unread,
Dec 6, 2017, 7:41:39 AM12/6/17
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation
wat?

#syz invalid

On Mon, Dec 4, 2017 at 7:22 AM, syzbot
<bot+f13a2fe20adf207007...@syzkaller.appspotmail.com>
wrote:
> --
> 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 post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a1143fd007dab8f055f7dbcab%40google.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages