Michael S. Tsirkin
2022-Sep-27 22:20 UTC
[syzbot] usb-testing boot error: BUG: unable to handle kernel paging request in virtnet_set_affinity
On Mon, Aug 22, 2022 at 12:48:32PM -0700, syzbot wrote:> Hello, > > syzbot found the following issue on: > > HEAD commit: ad57410d231d usb: gadget: rndis: use %u instead of %d to p.. > git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing > console output: https://syzkaller.appspot.com/x/log.txt?x=17472b85080000 > kernel config: https://syzkaller.appspot.com/x/.config?x=3cb39b084894e9a5 > dashboard link: https://syzkaller.appspot.com/bug?extid=0cb3309ee74d3c0c431c > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+0cb3309ee74d3c0c431c at syzkaller.appspotmail.com > > PCI-DMA: Using software bounce buffering for IO (SWIOTLB) > software IO TLB: mapped [mem 0x00000000bbffd000-0x00000000bfffd000] (64MB) > RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer > clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1fb6feccdd0, max_idle_ns: 440795259471 ns > clocksource: Switched to clocksource tsc > Initialise system trusted keyrings > workingset: timestamp_bits=40 max_order=21 bucket_order=0 > NFS: Registering the id_resolver key type > Key type id_resolver registered > Key type id_legacy registered > 9p: Installing v9fs 9p2000 file system support > Key type asymmetric registered > Asymmetric key parser 'x509' registered > Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) > io scheduler mq-deadline registered > io scheduler kyber registered > usbcore: registered new interface driver udlfb > usbcore: registered new interface driver smscufx > input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 > ACPI: button: Power Button [PWRF] > input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input1 > ACPI: button: Sleep Button [SLPF] > ACPI: \_SB_.LNKC: Enabled at IRQ 11 > virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver > ACPI: \_SB_.LNKD: Enabled at IRQ 10 > virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver > ACPI: \_SB_.LNKB: Enabled at IRQ 10 > virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver > virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled > 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A > 00:04: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A > 00:05: ttyS2 at I/O 0x3e8 (irq = 6, base_baud = 115200) is a 16550A > 00:06: ttyS3 at I/O 0x2e8 (irq = 7, base_baud = 115200) is a 16550A > Non-volatile memory driver v1.3 > Linux agpgart interface v0.103 > ACPI: bus type drm_connector registered > usbcore: registered new interface driver udl > loop: module loaded > usbcore: registered new interface driver rtsx_usb > usbcore: registered new interface driver viperboard > usbcore: registered new interface driver dln2 > usbcore: registered new interface driver pn533_usb > usbcore: registered new interface driver port100 > usbcore: registered new interface driver nfcmrvl > scsi host0: Virtio SCSI HBA > scsi 0:0:1:0: Direct-Access Google PersistentDisk 1 PQ: 0 ANSI: 6 > sd 0:0:1:0: Attached scsi generic sg0 type 0 > Rounding down aligned max_sectors from 4294967295 to 4294967288 > db_root: cannot open: /etc/target > BUG: unable to handle page fault for address: ffffdc0000000000 > #PF: supervisor read access in kernel mode > #PF: error_code(0x0000) - not-present page > PGD 100026067 P4D 100026067 PUD 0 > Oops: 0000 [#1] PREEMPT SMP KASAN > CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.0.0-rc1-syzkaller-00005-gad57410d231d #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022 > RIP: 0010:virtnet_set_affinity+0x2e4/0x600 drivers/net/virtio_net.c:2303 > Code: e8 03 42 80 3c 30 00 0f 85 de 02 00 00 48 8b 44 24 10 48 8d 1c 80 48 8b 44 24 18 48 c1 e3 08 48 03 58 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 0f 85 a9 02 00 00 4c 8b 23 49 8d 7c 24 20 48 89 f8 > RSP: 0000:ffffc9000001f980 EFLAGS: 00010a06 > RAX: 1fffe00000000000 RBX: ffff000000000000 RCX: 0000000000000000 > RDX: ffff8881002a8000 RSI: ffffffff82fd75e3 RDI: 0000000000000004 > RBP: 0000000000000001 R08: 0000000000000004 R09: 0000000000000001 > R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001 > R13: 0000000000000000 R14: dffffc0000000000 R15: ffffc9000001f9f8 > FS: 0000000000000000(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffffdc0000000000 CR3: 0000000007825000 CR4: 00000000003506e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > <TASK> > init_vqs drivers/net/virtio_net.c:3611 [inline] > init_vqs drivers/net/virtio_net.c:3597 [inline] > virtnet_probe+0x11ed/0x30f0 drivers/net/virtio_net.c:3904 > virtio_dev_probe+0x577/0x870 drivers/virtio/virtio.c:305 > call_driver_probe drivers/base/dd.c:530 [inline] > really_probe+0x249/0xb90 drivers/base/dd.c:609 > __driver_probe_device+0x1df/0x4d0 drivers/base/dd.c:748 > driver_probe_device+0x4c/0x1a0 drivers/base/dd.c:778 > __driver_attach+0x223/0x550 drivers/base/dd.c:1150 > bus_for_each_dev+0x147/0x1d0 drivers/base/bus.c:301 > bus_add_driver+0x4c9/0x640 drivers/base/bus.c:618 > driver_register+0x220/0x3a0 drivers/base/driver.c:240 > virtio_net_driver_init+0x93/0xd2 drivers/net/virtio_net.c:4108 > do_one_initcall+0xfe/0x650 init/main.c:1296 > do_initcall_level init/main.c:1369 [inline] > do_initcalls init/main.c:1385 [inline] > do_basic_setup init/main.c:1404 [inline] > kernel_init_freeable+0x6ac/0x735 init/main.c:1611 > kernel_init+0x1a/0x1d0 init/main.c:1500 > ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 > </TASK> > Modules linked in: > CR2: ffffdc0000000000 > ---[ end trace 0000000000000000 ]--- > RIP: 0010:virtnet_set_affinity+0x2e4/0x600 drivers/net/virtio_net.c:2303So this is not new it turns out. Was on vacation and missed it.> Code: e8 03 42 80 3c 30 00 0f 85 de 02 00 00 48 8b 44 24 10 48 8d 1c 80 48 8b 44 24 18 48 c1 e3 08 48 03 58 20 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 0f 85 a9 02 00 00 4c 8b 23 49 8d 7c 24 20 48 89 f8 > RSP: 0000:ffffc9000001f980 EFLAGS: 00010a06 > RAX: 1fffe00000000000 RBX: ffff000000000000 RCX: 0000000000000000 > RDX: ffff8881002a8000 RSI: ffffffff82fd75e3 RDI: 0000000000000004 > RBP: 0000000000000001 R08: 0000000000000004 R09: 0000000000000001 > R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001 > R13: 0000000000000000 R14: dffffc0000000000 R15: ffffc9000001f9f8 > FS: 0000000000000000(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: ffffdc0000000000 CR3: 0000000007825000 CR4: 00000000003506e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > ---------------- > Code disassembly (best guess): > 0: e8 03 42 80 3c callq 0x3c804208 > 5: 30 00 xor %al,(%rax) > 7: 0f 85 de 02 00 00 jne 0x2eb > d: 48 8b 44 24 10 mov 0x10(%rsp),%rax > 12: 48 8d 1c 80 lea (%rax,%rax,4),%rbx > 16: 48 8b 44 24 18 mov 0x18(%rsp),%rax > 1b: 48 c1 e3 08 shl $0x8,%rbx > 1f: 48 03 58 20 add 0x20(%rax),%rbx > 23: 48 89 d8 mov %rbx,%rax > 26: 48 c1 e8 03 shr $0x3,%rax > * 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction > 2f: 0f 85 a9 02 00 00 jne 0x2de > 35: 4c 8b 23 mov (%rbx),%r12 > 38: 49 8d 7c 24 20 lea 0x20(%r12),%rdi > 3d: 48 89 f8 mov %rdi,%rax > > > --- > 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 syzkaller at googlegroups.com. > > syzbot will keep track of this issue. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot.