[syzbot] [kernel?] WARNING in flush_cpu_slab (2)

[syzbot <syzbot+6eb04f338c0358f11050@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    a99b4a369a54 Merge tag 'pci-v6.13-fixes-2' of git://git.ke..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=139b1fe8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=6eb04f338c0358f11050
compiler:       Debian clang version 15.0.6, 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/429b293cfc4d/disk-a99b4a36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6ecf52e676b2/vmlinux-a99b4a36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b4ff2ac886d/bzImage-a99b4a36.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6eb04f338c0358f11050@syzkaller.appspotmail.com

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(l->owner)
WARNING: CPU: 1 PID: 969 at ./include/linux/local_lock_internal.h:30 local_lock_acquire include/linux/local_lock_internal.h:30 [inline]
WARNING: CPU: 1 PID: 969 at ./include/linux/local_lock_internal.h:30 flush_slab mm/slub.c:3251 [inline]
WARNING: CPU: 1 PID: 969 at ./include/linux/local_lock_internal.h:30 flush_cpu_slab+0x39e/0x450 mm/slub.c:3309
Modules linked in:
CPU: 1 UID: 0 PID: 969 Comm: kworker/1:2 Not tainted 6.13.0-rc3-syzkaller-00237-ga99b4a369a54 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: slub_flushwq flush_cpu_slab
RIP: 0010:local_lock_acquire include/linux/local_lock_internal.h:30 [inline]
RIP: 0010:flush_slab mm/slub.c:3251 [inline]
RIP: 0010:flush_cpu_slab+0x39e/0x450 mm/slub.c:3309
Code: ff ff 90 e8 24 b9 c3 02 85 c0 74 22 83 3d 8d b3 1e 0e 00 75 19 90 48 c7 c7 6e 70 06 8e 48 c7 c6 d2 c3 06 8e e8 13 1b 65 ff 90 <0f> 0b 90 90 90 e9 22 fd ff ff 90 e8 f2 b8 c3 02 85 c0 74 22 83 3d
RSP: 0018:ffffc90003b7fb58 EFLAGS: 00010046
RAX: 10f2a25ca633b400 RBX: ffffe8ffffd8d2f0 RCX: ffff888026943c00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff81601a42 R09: fffffbfff1cfa210
R10: dffffc0000000000 R11: fffffbfff1cfa210 R12: 0000607f4768d2d0
R13: ffffffff8168ee96 R14: ffff8880b8700000 R15: ffff88804d79b3c0
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3f1d29 CR3: 000000004f5da000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa68/0x1840 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f2/0x390 kernel/kthread.c:389
 ret_from_fork+0x4d/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@googlegroups.com.

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