syzbot


general protection fault in relay_switch_subbuf

Status: auto-closed as invalid on 2019/12/15 08:14
Reported-by: syzbot+adc5b8186062540592ce@syzkaller.appspotmail.com
First crash: 1876d, last: 1876d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 general protection fault in relay_switch_subbuf 2 1653d 1746d 0/1 auto-closed as invalid on 2020/07/25 03:12
upstream KASAN: use-after-free Read in relay_switch_subbuf block trace C done error 93 707d 2201d 0/28 auto-obsoleted due to no activity on 2023/04/20 06:56
upstream general protection fault in relay_switch_subbuf block trace 4 2080d 2053d 0/28 auto-closed as invalid on 2019/07/23 22:29
upstream general protection fault in relay_switch_subbuf (2) block trace 1 1893d 1885d 0/28 auto-closed as invalid on 2019/10/25 14:11
linux-5.15 KASAN: use-after-free Read in relay_switch_subbuf 2 520d 540d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:04
upstream general protection fault in relay_switch_subbuf (3) block trace 1 1801d 1800d 0/28 auto-closed as invalid on 2020/01/29 10:20
linux-4.19 general protection fault in relay_switch_subbuf (2) 1 1573d 1573d 0/1 auto-closed as invalid on 2020/10/13 07:52
linux-4.19 KASAN: use-after-free Read in relay_switch_subbuf (2) 23 601d 1083d 0/1 upstream: reported on 2021/10/17 18:33

Sample crash report:
EXT4-fs warning (device sda1): ext4_group_extend:1793: will only finish group (524288 blocks, 256 new)
print_req_error: I/O error, dev loop0, 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
kobject: 'kvm' (00000000f3a54013): kobject_uevent_env
CPU: 1 PID: 21185 Comm: syz-executor.0 Not tainted 4.19.67 #41
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:relay_switch_subbuf+0x216/0x920 kernel/relay.c:755
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bc 06 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 7b 58 49 8d 7f 50 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7d 06 00 00 48 ba 00 00 00 00 00 fc ff df 49 8b
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
RSP: 0018:ffff888089377870 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: ffff8880971c9420 RCX: ffffc90006078000
EXT4-fs warning (device sda1): ext4_group_extend:1799: can't read last block, resize aborted
RDX: 000000000000000a RSI: ffffffff816bf53e RDI: 0000000000000050
RBP: ffff8880893778c8 R08: ffff88805bf1e500 R09: 0000000000000010
R10: fffffbfff10c1b70 R11: ffffffff8860db83 R12: 0000000000000040
R13: 0000000000000000 R14: ffff8880934c8c80 R15: 0000000000000000
FS:  00007f48eacf1700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000075c000 CR3: 0000000096190000 CR4: 00000000001426e0
kobject: 'kvm' (00000000f3a54013): fill_kobj_path: path = '/devices/virtual/misc/kvm'
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 relay_reserve include/linux/relay.h:261 [inline]
 trace_note.isra.0+0x5b8/0x6e0 kernel/trace/blktrace.c:93
 trace_note_tsk kernel/trace/blktrace.c:124 [inline]
 __blk_add_trace+0xb70/0xe10 kernel/trace/blktrace.c:264
CPU: 0 PID: 21186 Comm: syz-executor.5 Not tainted 4.19.67 #41
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
 blk_add_trace_bio.isra.0+0x166/0x1e0 kernel/trace/blktrace.c:870
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 blk_add_trace_bio_queue+0x46/0x60 kernel/trace/blktrace.c:907
 fail_dump lib/fault-inject.c:51 [inline]
 should_fail.cold+0xa/0x1b lib/fault-inject.c:149
 trace_block_bio_queue include/trace/events/block.h:357 [inline]
 generic_make_request_checks+0x1cc2/0x24c0 block/blk-core.c:2339
 generic_make_request+0x24c/0x12d0 block/blk-core.c:2405
 submit_bio+0xba/0x480 block/blk-core.c:2569
 submit_bio_wait+0x115/0x1c0 block/bio.c:930
 blkdev_issue_flush+0x20b/0x300 block/blk-flush.c:553
 blkdev_fsync+0x95/0xd0 fs/block_dev.c:647
 vfs_fsync_range+0x141/0x230 fs/sync.c:197
 vfs_fsync fs/sync.c:211 [inline]
 do_fsync+0x54/0xa0 fs/sync.c:221
 __do_sys_fdatasync fs/sync.c:234 [inline]
 __se_sys_fdatasync fs/sync.c:232 [inline]
 __x64_sys_fdatasync+0x36/0x50 fs/sync.c:232
 do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459829
Code: fd b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 cb b7 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f48eacf0c78 EFLAGS: 00000246
 __should_failslab+0x121/0x190 mm/failslab.c:32
 ORIG_RAX: 000000000000004b
 should_failslab+0x9/0x14 mm/slab_common.c:1557
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 0000000000459829
 slab_pre_alloc_hook mm/slab.h:424 [inline]
 slab_alloc mm/slab.c:3383 [inline]
 kmem_cache_alloc+0x2ae/0x700 mm/slab.c:3557
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
 kmem_cache_zalloc include/linux/slab.h:699 [inline]
 mmu_topup_memory_cache arch/x86/kvm/mmu.c:933 [inline]
 mmu_topup_memory_cache arch/x86/kvm/mmu.c:925 [inline]
 mmu_topup_memory_caches+0x97/0x3a0 arch/x86/kvm/mmu.c:979
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f48eacf16d4
 kvm_mmu_load+0x21/0xf60 arch/x86/kvm/mmu.c:4968
R13: 00000000004c00c7 R14: 00000000004d2190 R15: 00000000ffffffff
Modules linked in:
 kvm_mmu_reload arch/x86/kvm/mmu.h:86 [inline]
 vcpu_enter_guest+0x3cdb/0x6120 arch/x86/kvm/x86.c:7600
---[ end trace e4643273033d4fea ]---
RIP: 0010:relay_switch_subbuf+0x216/0x920 kernel/relay.c:755
Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bc 06 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 7b 58 49 8d 7f 50 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7d 06 00 00 48 ba 00 00 00 00 00 fc ff df 49 8b
RSP: 0018:ffff888089377870 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: ffff8880971c9420 RCX: ffffc90006078000
 vcpu_run arch/x86/kvm/x86.c:7798 [inline]
 kvm_arch_vcpu_ioctl_run+0x457/0x16b0 arch/x86/kvm/x86.c:7998
RDX: 000000000000000a RSI: ffffffff816bf53e RDI: 0000000000000050
RBP: ffff8880893778c8 R08: ffff88805bf1e500 R09: 0000000000000010
 kvm_vcpu_ioctl+0x4dc/0xf90 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2617
R10: fffffbfff10c1b70 R11: ffffffff8860db83 R12: 0000000000000040
R13: 0000000000000000 R14: ffff8880934c8c80 R15: 0000000000000000
FS:  00007f48eacf1700(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000075c000 CR3: 0000000096190000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:501 [inline]
 do_vfs_ioctl+0xd5f/0x1380 fs/ioctl.c:688

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/08/17 08:13 linux-4.19.y a5aa80588fcd 8fd428a1 .config console log report ci2-linux-4-19
* Struck through repros no longer work on HEAD.