syzbot


BUG: unable to handle kernel paging request in ft260_smbus_xfer

Status: upstream: reported C repro on 2024/07/27 16:16
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+f3bd7d0fae73299f4f70@syzkaller.appspotmail.com
First crash: 55d, last: 19d
Bug presence (2)
Date Name Commit Repro Result
2024/07/27 linux-5.15.y (ToT) 7e89efd3ae1c C [report] BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 upstream (ToT) ff30564411ff C Didn't crash
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/08/02 05:58 1m fix candidate upstream error job log

Sample crash report:
ft260 0003:0403:6030.0001: unknown main item tag 0x0
ft260 0003:0403:6030.0001: hidraw0: USB HID v0.00 Device [HID 0403:6030] on usb-dummy_hcd.0-1/input0
ft260 0003:0403:6030.0001: chip code: 5e81 abf2
Unable to handle kernel paging request at virtual address dfff8000000000fa
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
[dfff8000000000fa] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 1534 Comm: kworker/1:2 Not tainted 5.15.164-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/2024
Workqueue: usb_hub_wq hub_event
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ft260_smbus_xfer+0x6c/0x126c drivers/hid/hid-ft260.c:602
lr : ft260_smbus_xfer+0x48/0x126c drivers/hid/hid-ft260.c:599
sp : ffff800020975ea0
x29: ffff800020975ec0 x28: 0000000000000000 x27: 0000000000000000
x26: 1fffe000191af835 x25: 0000000000000000 x24: ffff0000c8d7c1a8
x23: dfff800000000000 x22: 0000000000000000 x21: 00000000ffff9a0c
x20: 1ffff00002947e30 x19: 00000000000007d0 x18: ffff800020975ca0
x17: 0000000000000000 x16: ffff800011ab8a28 x15: 000000000000c5f6
x14: 00000000324e762d x13: dfff800000000000 x12: 0000f2f2f2f2f202
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000cca13680
x8 : 00000000000000fa x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000018 x0 : ffff0000c8d7c080
Call trace:
 ft260_smbus_xfer+0x6c/0x126c drivers/hid/hid-ft260.c:602
 __i2c_smbus_xfer+0x570/0x2b70 drivers/i2c/i2c-core-smbus.c:589
 i2c_smbus_xfer+0x210/0x31c drivers/i2c/i2c-core-smbus.c:544
 i2c_default_probe+0x1c0/0x248
 i2c_detect_address drivers/i2c/i2c-core-base.c:2408 [inline]
 i2c_detect drivers/i2c/i2c-core-base.c:2483 [inline]
 i2c_do_add_adapter+0x3c4/0x8d4 drivers/i2c/i2c-core-base.c:1372
 __process_new_adapter+0x28/0x3c drivers/i2c/i2c-core-base.c:1379
 bus_for_each_drv+0x158/0x1e0 drivers/base/bus.c:427
 i2c_register_adapter+0xcc8/0xf8c drivers/i2c/i2c-core-base.c:1542
 i2c_add_adapter+0x170/0x250
 ft260_probe+0x3f0/0x570 drivers/hid/hid-ft260.c:972
 hid_device_probe+0x23c/0x338 drivers/hid/hid-core.c:2307
 really_probe+0x26c/0xaec drivers/base/dd.c:595
 __driver_probe_device+0x194/0x3b4 drivers/base/dd.c:755
 driver_probe_device+0x78/0x34c drivers/base/dd.c:785
 __device_attach_driver+0x28c/0x4d8 drivers/base/dd.c:907
 bus_for_each_drv+0x158/0x1e0 drivers/base/bus.c:427
 __device_attach+0x2f0/0x480 drivers/base/dd.c:979
 device_initial_probe+0x24/0x34 drivers/base/dd.c:1028
 bus_probe_device+0xbc/0x1c8 drivers/base/bus.c:487
 device_add+0xae0/0xef4 drivers/base/core.c:3412
 hid_add_device+0x318/0x4b4 drivers/hid/hid-core.c:2459
 usbhid_probe+0x868/0xba8 drivers/hid/usbhid/hid-core.c:1424
 usb_probe_interface+0x500/0x984 drivers/usb/core/driver.c:396
 really_probe+0x26c/0xaec drivers/base/dd.c:595
 __driver_probe_device+0x194/0x3b4 drivers/base/dd.c:755
 driver_probe_device+0x78/0x34c drivers/base/dd.c:785
 __device_attach_driver+0x28c/0x4d8 drivers/base/dd.c:907
 bus_for_each_drv+0x158/0x1e0 drivers/base/bus.c:427
 __device_attach+0x2f0/0x480 drivers/base/dd.c:979
 device_initial_probe+0x24/0x34 drivers/base/dd.c:1028
 bus_probe_device+0xbc/0x1c8 drivers/base/bus.c:487
 device_add+0xae0/0xef4 drivers/base/core.c:3412
 usb_set_configuration+0x15e0/0x1b60 drivers/usb/core/message.c:2165
 usb_generic_driver_probe+0x8c/0x148 drivers/usb/core/generic.c:238
 usb_probe_device+0x120/0x25c drivers/usb/core/driver.c:293
 really_probe+0x26c/0xaec drivers/base/dd.c:595
 __driver_probe_device+0x194/0x3b4 drivers/base/dd.c:755
 driver_probe_device+0x78/0x34c drivers/base/dd.c:785
 __device_attach_driver+0x28c/0x4d8 drivers/base/dd.c:907
 bus_for_each_drv+0x158/0x1e0 drivers/base/bus.c:427
 __device_attach+0x2f0/0x480 drivers/base/dd.c:979
 device_initial_probe+0x24/0x34 drivers/base/dd.c:1028
 bus_probe_device+0xbc/0x1c8 drivers/base/bus.c:487
 device_add+0xae0/0xef4 drivers/base/core.c:3412
 usb_new_device+0x900/0x145c drivers/usb/core/hub.c:2593
 hub_port_connect drivers/usb/core/hub.c:5455 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5595 [inline]
 port_event drivers/usb/core/hub.c:5741 [inline]
 hub_event+0x236c/0x46b8 drivers/usb/core/hub.c:5823
 process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
 worker_thread+0x910/0x1034 kernel/workqueue.c:2457
 kthread+0x37c/0x45c kernel/kthread.c:334
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: 96513479 f9400276 911f42d3 d343fe68 (38776908) 
---[ end trace c10ef1ab47d2b211 ]---
----------------
Code disassembly (best guess):
   0:	96513479 	bl	0xfffffffff944d1e4
   4:	f9400276 	ldr	x22, [x19]
   8:	911f42d3 	add	x19, x22, #0x7d0
   c:	d343fe68 	lsr	x8, x19, #3
* 10:	38776908 	ldrb	w8, [x8, x23] <-- trapping instruction

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/07/27 23:41 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 22:31 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 20:54 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 19:26 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 17:55 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/09/01 15:53 linux-5.15.y fa93fa65db6e 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/08/08 09:01 linux-5.15.y 7e89efd3ae1c de12cf65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/08/03 15:16 linux-5.15.y 7e89efd3ae1c 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 16:20 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
2024/07/27 16:15 linux-5.15.y 7e89efd3ae1c 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_smbus_xfer
* Struck through repros no longer work on HEAD.