Hello, syzbot found the following issue on: HEAD commit: f44d154d6e3d Merge tag 'soc-fixes-6.13' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=128282df980000 kernel config: https://syzkaller.appspot.com/x/.config?x=c22efbd20f8da769 dashboard link: https://syzkaller.appspot.com/bug?extid=48d64503fdea9b2ee378 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/129158790532/disk-f44d154d.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4893f23f2c39/vmlinux-f44d154d.xz kernel image: https://storage.googleapis.com/syzbot-assets/b12b565fb71e/bzImage-f44d154d.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+48d64503fdea9b2ee378@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ wlan1: Failed check-sdata-in-driver check, flags: 0x0 WARNING: CPU: 0 PID: 2894 at net/mac80211/driver-ops.c:249 drv_get_tsf+0x1c7/0x780 net/mac80211/driver-ops.c:249 Modules linked in: CPU: 0 UID: 0 PID: 2894 Comm: kworker/u8:6 Not tainted 6.13.0-rc3-syzkaller-00017-gf44d154d6e3d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 Workqueue: events_unbound cfg80211_wiphy_work RIP: 0010:drv_get_tsf+0x1c7/0x780 net/mac80211/driver-ops.c:249 Code: 0f 84 44 05 00 00 e8 38 93 0c f7 49 81 c4 20 01 00 00 e8 2c 93 0c f7 44 89 f2 4c 89 e6 48 c7 c7 40 f6 9d 8c e8 5a 59 cd f6 90 <0f> 0b 90 90 e8 10 93 0c f7 4c 89 ea 48 b8 00 00 00 00 00 fc ff df RSP: 0018:ffffc9000c337c00 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff888024f68d80 RCX: ffffffff815a16c9 RDX: ffff888030430000 RSI: ffffffff815a16d6 RDI: 0000000000000001 RBP: ffff888024ea0e40 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffff888024f68120 R13: ffff888024f69728 R14: 0000000000000000 R15: ffff888024ea06a8 FS: 0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000110c3d933b CR3: 000000002fde0000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ieee80211_if_fmt_tsf+0x42/0x70 net/mac80211/debugfs_netdev.c:661 wiphy_locked_debugfs_read_work+0xe3/0x1c0 net/wireless/debugfs.c:135 cfg80211_wiphy_work+0x3de/0x560 net/wireless/core.c:440 process_one_work+0x958/0x1b30 kernel/workqueue.c:3229 process_scheduled_works kernel/workqueue.c:3310 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3391 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> --- 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@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
