Hello,
syzbot found the following crash on:
HEAD commit: f66ed1eb Merge tag 'iomap-5.7-fixes-1' of git://git.kernel..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=116c9ec4100000
kernel config:
https://syzkaller.appspot.com/x/.config?x=1ac152749c11ca54
dashboard link:
https://syzkaller.appspot.com/bug?extid=6a3705498ca5ec807419
compiler: clang version 10.0.0 (
https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
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+6a3705...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: null-ptr-deref in syscall_get_arguments arch/x86/include/asm/syscall.h:114 [inline]
BUG: KASAN: null-ptr-deref in trace_event_raw_event_sys_enter+0x29a/0x440 include/trace/events/syscalls.h:18
Write of size 8 at addr 0000000000000000 by task syz-executor.5/19972
CPU: 0 PID: 19972 Comm: syz-executor.5 Not tainted 5.7.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1e9/0x30e lib/dump_stack.c:118
__kasan_report+0x122/0x1a0 mm/kasan/report.c:515
kasan_report+0x4d/0x80 mm/kasan/common.c:625
</IRQ>
==================================================================
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 19972 Comm: syz-executor.5 Tainted: G B 5.7.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1e9/0x30e lib/dump_stack.c:118
panic+0x264/0x7a0 kernel/panic.c:221
end_report mm/kasan/report.c:103 [inline]
__kasan_report+0x191/0x1a0 mm/kasan/report.c:518
kasan_report+0x4d/0x80 mm/kasan/common.c:625
</IRQ>
Shutting down cpus with NMI
Kernel Offset: disabled
---
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#status for how to communicate with syzbot.