From: syzbot <syzbot+0192952caa411a3be209@syzkaller.appspotmail.com>
To: aha310510@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer
Date: Fri, 05 Sep 2025 08:53:04 -0700 [thread overview]
Message-ID: <68bb0760.a00a0220.eb3d.0017.GAE@google.com> (raw)
In-Reply-To: <20250905142535.4117869-1-aha310510@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in az6007_identify_state
usb 2-1: config 0 descriptor??
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:577 __mutex_lock_common kernel/locking/mutex.c:577 [inline]
WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:577 __mutex_lock+0x3a2/0x1060 kernel/locking/mutex.c:760
Modules linked in:
CPU: 0 UID: 0 PID: 10 Comm: kworker/0:1 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: usb_hub_wq hub_event
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:577 [inline]
RIP: 0010:__mutex_lock+0x3a2/0x1060 kernel/locking/mutex.c:760
Code: 08 84 d2 0f 85 7e 0c 00 00 44 8b 0d 78 89 1a 05 45 85 c9 75 19 90 48 c7 c6 20 57 ad 8b 48 c7 c7 60 56 ad 8b e8 ff 11 ea f5 90 <0f> 0b 90 90 90 e9 b5 fd ff ff 48 8d 85 60 ff ff ff 48 89 df 48 89
RSP: 0018:ffffc900000f6de0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff888032d9c000 RCX: ffffffff817a2388
RDX: ffff88801e2c8000 RSI: ffffffff817a2395 RDI: 0000000000000001
RBP: ffffc900000f6f30 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: dffffc0000000000
R13: 0000000000000000 R14: 1ffff9200001edc8 R15: ffffffff8800f287
FS: 0000000000000000(0000) GS:ffff8881246e3000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ac14aafab0 CR3: 000000007d1e6000 CR4: 00000000003526f0
Call Trace:
<TASK>
az6007_read drivers/media/usb/dvb-usb-v2/az6007.c:138 [inline]
az6007_identify_state+0x97/0x310 drivers/media/usb/dvb-usb-v2/az6007.c:865
dvb_usbv2_probe+0x4cc/0x3e50 drivers/media/usb/dvb-usb-v2/dvb_usb_core.c:947
usb_probe_interface+0x300/0xa40 drivers/usb/core/driver.c:396
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x241/0xa90 drivers/base/dd.c:659
__driver_probe_device+0x1de/0x440 drivers/base/dd.c:801
driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:831
__device_attach_driver+0x1df/0x310 drivers/base/dd.c:959
bus_for_each_drv+0x159/0x1e0 drivers/base/bus.c:462
__device_attach+0x1e4/0x4b0 drivers/base/dd.c:1031
bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:537
device_add+0x1148/0x1aa0 drivers/base/core.c:3689
usb_set_configuration+0x1187/0x1e20 drivers/usb/core/message.c:2210
usb_generic_driver_probe+0xb1/0x110 drivers/usb/core/generic.c:250
usb_probe_device+0xef/0x3e0 drivers/usb/core/driver.c:291
call_driver_probe drivers/base/dd.c:581 [inline]
really_probe+0x241/0xa90 drivers/base/dd.c:659
__driver_probe_device+0x1de/0x440 drivers/base/dd.c:801
driver_probe_device+0x4c/0x1b0 drivers/base/dd.c:831
__device_attach_driver+0x1df/0x310 drivers/base/dd.c:959
bus_for_each_drv+0x159/0x1e0 drivers/base/bus.c:462
__device_attach+0x1e4/0x4b0 drivers/base/dd.c:1031
bus_probe_device+0x17f/0x1c0 drivers/base/bus.c:537
device_add+0x1148/0x1aa0 drivers/base/core.c:3689
usb_new_device+0xd07/0x1a60 drivers/usb/core/hub.c:2694
hub_port_connect drivers/usb/core/hub.c:5566 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5706 [inline]
port_event drivers/usb/core/hub.c:5870 [inline]
hub_event+0x2f34/0x4fe0 drivers/usb/core/hub.c:5952
process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3236
process_scheduled_works kernel/workqueue.c:3319 [inline]
worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
kthread+0x3c2/0x780 kernel/kthread.c:463
ret_from_fork+0x5d4/0x6f0 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: d69eb204 Merge tag 'net-6.17-rc5' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=112dc962580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2b271b97d244fd0a
dashboard link: https://syzkaller.appspot.com/bug?extid=0192952caa411a3be209
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12c9c962580000
next prev parent reply other threads:[~2025-09-05 15:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 1:41 [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 13:40 ` syz test Arnaud Lecomte
2025-04-21 13:44 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 13:43 ` Edward Adam Davis
2025-04-21 14:25 ` syzbot
2025-04-21 13:46 ` syz test Arnaud Lecomte
2025-04-21 14:58 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:22 ` syz test Arnaud Lecomte
2025-04-21 16:12 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:31 ` [PATCH] media: az6007: Add upper bound check to the data of device state Edward Adam Davis
2025-04-21 15:11 ` Arnaud Lecomte
2025-11-03 10:06 ` Hans Verkuil
2025-09-05 14:25 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer Jeongjun Park
2025-09-05 15:53 ` syzbot [this message]
2025-09-05 16:06 ` Jeongjun Park
2025-09-05 16:48 ` syzbot
2025-09-06 2:58 ` Jeongjun Park
2025-09-06 3:16 ` syzbot
2025-09-06 3:32 ` Jeongjun Park
2025-09-06 4:12 ` syzbot
2025-09-06 4:56 ` Jeongjun Park
2025-09-06 5:54 ` syzbot
2025-09-06 10:04 ` Jeongjun Park
2025-09-06 10:24 ` syzbot
2025-09-06 10:56 ` Jeongjun Park
2025-09-06 12:28 ` syzbot
2025-09-06 15:24 ` Jeongjun Park
2025-09-06 16:09 ` syzbot
2025-09-06 16:40 ` Jeongjun Park
2025-09-06 17:21 ` syzbot
2025-09-07 8:26 ` Jeongjun Park
2025-09-07 9:56 ` syzbot
2025-09-07 10:05 ` Jeongjun Park
2025-09-07 10:30 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68bb0760.a00a0220.eb3d.0017.GAE@google.com \
--to=syzbot+0192952caa411a3be209@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.