Hello,
syzbot found the following issue on:
HEAD commit: 5b7a52cd Linux 4.14.202
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=15629a8c500000
kernel config:
https://syzkaller.appspot.com/x/.config?x=fa386e02ca459165
dashboard link:
https://syzkaller.appspot.com/bug?extid=2be7d1f1055673413f63
compiler: gcc (GCC) 10.1.0-syz 20200507
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+2be7d1...@syzkaller.appspotmail.com
print_req_error: I/O error, dev loop1, sector 0
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 8005 Comm: syz-executor.0 Not tainted 4.14.202-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880660b6540 task.stack: ffff8880660b8000
RIP: 0010:kobject_uevent_env+0xb2/0xf40 lib/kobject_uevent.c:355
RSP: 0018:ffff8880660bfb28 EFLAGS: 00010206
RAX: 0000000000000018 RBX: 0000000000000002 RCX: 1ffff1100cc16dbe
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 00000000000000c0
RBP: ffff8880a540f010 R08: ffffffff8b9a0038 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880660b6540 R12: 00000000000000a0
R13: dffffc0000000000 R14: ffff8880a540ef08 R15: 00000000000000a0
FS: 0000000001f31940(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000564b34e5cd48 CR3: 000000006607a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
loop_clr_fd+0x59f/0xc20 drivers/block/loop.c:1069
lo_ioctl+0x895/0x1cd0 drivers/block/loop.c:1424
__blkdev_driver_ioctl block/ioctl.c:297 [inline]
blkdev_ioctl+0x540/0x1830 block/ioctl.c:594
block_ioctl+0xd9/0x120 fs/block_dev.c:1893
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45dcc7
RSP: 002b:00007ffd2afef608 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045dcc7
RDX: 0000000000000000 RSI: 0000000000004c01 RDI: 0000000000000003
RBP: 0000000000000712 R08: 0000000000000000 R09: 000000000000000a
R10: 0000000000000075 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd2afef640 R14: 00000000000602a6 R15: 00007ffd2afef650
Code: 03 42 80 3c 28 00 0f 85 e4 0b 00 00 4d 8b 64 24 18 4d 85 e4 0f 84 01 0c 00 00 e8 ba 61 3c fa 49 8d 7c 24 20 48 89 f8 48 c1 e8 03 <42> 80 3c 28 00 0f 85 db 0b 00 00 49 8b 6c 24 20 48 85 ed 74 b0
RIP: kobject_uevent_env+0xb2/0xf40 lib/kobject_uevent.c:355 RSP: ffff8880660bfb28
---[ end trace 09ccb9088afcca0b ]---
---
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.