Hello,
syzbot hit the following crash on upstream commit
c89be5242607d8aa08a6fa45a887c68b2d4a2a2c (Sun Feb 25 21:43:18 2018 +0000)
Merge tag 'nfs-for-4.16-3' of
git://
git.linux-nfs.org/projects/trondmy/linux-nfs
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
CC: [
alsa-...@alsa-project.org linux-...@vger.kernel.org
ma...@maciej.szmigiero.name o-ta...@sakamocchi.jp pe...@perex.cz
ti...@suse.com]
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by:
syzbot+3f3eb6...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
BUG: unable to handle kernel paging request at ffffc9000163c000
IP: memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:65
PGD 1dad2f067 P4D 1dad2f067 PUD 1dad30067 PMD 1bc55a067 PTE 0
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 20058 Comm: syz-executor4 Not tainted 4.16.0-rc2+ #329
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:65
RSP: 0018:ffff8801b41ef3b8 EFLAGS: 00010246
RAX: fffff520002e7a00 RBX: ffffc90001639000 RCX: 0000000000101500
RDX: 0000000000104500 RSI: 0000000000000000 RDI: ffffc9000163c000
RBP: ffff8801b41ef3d8 R08: 0000000000000000 R09: ffffc90001639000
R10: 00000000000208a0 R11: fffff520002e7a9f R12: 0000000000104500
R13: 0000000000000000 R14: ffffffff874d321c R15: 0000000000000010
FS: 00007f93369ab700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9000163c000 CR3: 00000001ab32d006 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
memset include/linux/string.h:330 [inline]
snd_pcm_format_set_silence+0x13f/0x4b0 sound/core/pcm_misc.c:431
loopback_prepare+0x922/0xbe0 sound/drivers/aloop.c:340
snd_pcm_do_prepare+0x58/0x90 sound/core/pcm_native.c:1640
snd_pcm_action_single+0x70/0x110 sound/core/pcm_native.c:1084
snd_pcm_action_nonatomic+0x95/0xa0 sound/core/pcm_native.c:1151
snd_pcm_prepare+0x115/0x1a0 sound/core/pcm_native.c:1687
snd_pcm_kernel_ioctl+0x97/0x240 sound/core/pcm_native.c:2998
snd_pcm_oss_prepare+0x49/0x150 sound/core/oss/pcm_oss.c:1104
snd_pcm_oss_make_ready+0xf9/0x130 sound/core/oss/pcm_oss.c:1132
snd_pcm_oss_set_trigger+0x62d/0x830 sound/core/oss/pcm_oss.c:1957
snd_pcm_oss_poll+0x77c/0xd20 sound/core/oss/pcm_oss.c:2725
do_pollfd fs/select.c:826 [inline]
do_poll fs/select.c:877 [inline]
do_sys_poll+0x719/0x1050 fs/select.c:971
SYSC_poll fs/select.c:1029 [inline]
SyS_poll+0x10d/0x450 fs/select.c:1017
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007f93369aac68 EFLAGS: 00000246 ORIG_RAX: 0000000000000007
RAX: ffffffffffffffda RBX: 00007f93369ab6d4 RCX: 0000000000453de9
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000020009fe0
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000043c R14: 00000000006f6640 R15: 0000000000000000
Code: 48 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3
48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89
c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01
RIP: memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:65 RSP: ffff8801b41ef3b8
CR2: ffffc9000163c000
---[ end trace 1457b32d9fb5c93b ]---
---
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.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, 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