Hello,
syzbot found the following issue on:
HEAD commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://
git.ke..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=1493ff80a80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=db74cd5aa6878807
dashboard link:
https://syzkaller.appspot.com/bug?extid=80d2fea6b0a323f3e7cd
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [
bra...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable):
https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-a901a356.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ab583c97152f/vmlinux-a901a356.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/5b50cfdcec38/bzImage-a901a356.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+80d2fe...@syzkaller.appspotmail.com
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: do_epoll_wait+0x16e9/0x1910 fs/eventpoll.c:2331
CPU: 3 PID: 7689 Comm: udevd Not tainted 6.4.0-syzkaller-10173-ga901a3568fd2 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
panic+0x686/0x730 kernel/panic.c:340
__stack_chk_fail+0x19/0x20 kernel/panic.c:758
do_epoll_wait+0x16e9/0x1910 fs/eventpoll.c:2331
__do_sys_epoll_wait fs/eventpoll.c:2338 [inline]
__se_sys_epoll_wait fs/eventpoll.c:2333 [inline]
__x64_sys_epoll_wait+0x15c/0x280 fs/eventpoll.c:2333
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fcde3123457
Code: 73 01 c3 48 8b 0d d1 d9 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 20 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 76 76 48 8b 15 a2 d9 0c 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffcb1105b38 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcde3123457
RDX: 0000000000000004 RSI: 00007ffcb1105b78 RDI: 0000000000000004
RBP: 00005615ba250e10 R08: 0000000000000007 R09: 62d3fbbfb7e1ca23
R10: 00000000ffffffff R11: 0000000000000246 R12: 00005615ba29f220
R13: 00007ffcb1105b78 R14: 0000000000000008 R15: 00005615ba2322c0
</TASK>
---
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.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup