[syzbot] [kernel?] kernel BUG in deactivate_slab

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 54f71b0369c9 Merge tag 'rtc-6.10' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17b53a34980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e70c03a304f3c3ef
dashboard link: https://syzkaller.appspot.com/bug?extid=3ca210d193a9b5978ec2
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-54f71b03.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5bc3c5654135/vmlinux-54f71b03.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d88013021348/bzImage-54f71b03.xz

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

------------[ cut here ]------------
kernel BUG at mm/slub.c:2923!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 5293 Comm: kworker/2:4 Not tainted 6.9.0-syzkaller-12333-g54f71b0369c9 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: slub_flushwq flush_cpu_slab
RIP: 0010:deactivate_slab+0x350/0x4a0 mm/slub.c:2923
Code: de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 7a 5a fe 08 f3 90 4d 8b 6f 20 4d 8b 77 28 4c 89 f1 48 c1 e9 18 84 c9 0f 88 61 fe ff ff 90 <0f> 0b 48 8b 4c 24 20 4c 89 e8 4c 89 f2 f0 49 0f c7 4f 20 41 0f 94
RSP: 0018:ffffc900043f7bb0 EFLAGS: 00010246
RAX: 14ffff88805d9880 RBX: ffff88805d98f8c0 RCX: 000000ff00000000
RDX: ffffc900043f7c20 RSI: ffff88805d988000 RDI: 00000000000004a8
RBP: ffffc900043f7c88 R08: 0000000000000001 R09: 0000000000000014
R10: ffff88805d98f8c0 R11: 0000000000000001 R12: ffff888025b61cc0
R13: 0000000000000000 R14: ffffea0001766201 R15: ff00000000801800
FS: 0000000000000000(0000) GS:ffff88802c200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000edc6be00 CR3: 000000004b302000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
flush_slab mm/slub.c:3100 [inline]
flush_cpu_slab+0x141/0x410 mm/slub.c:3146
process_one_work+0x958/0x1ad0 kernel/workqueue.c:3231
process_scheduled_works kernel/workqueue.c:3312 [inline]
worker_thread+0x6c8/0xf70 kernel/workqueue.c:3393
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>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:deactivate_slab+0x350/0x4a0 mm/slub.c:2923
Code: de 5b 41 5c 41 5d 41 5e 41 5f 5d e9 7a 5a fe 08 f3 90 4d 8b 6f 20 4d 8b 77 28 4c 89 f1 48 c1 e9 18 84 c9 0f 88 61 fe ff ff 90 <0f> 0b 48 8b 4c 24 20 4c 89 e8 4c 89 f2 f0 49 0f c7 4f 20 41 0f 94
RSP: 0018:ffffc900043f7bb0 EFLAGS: 00010246
RAX: 14ffff88805d9880 RBX: ffff88805d98f8c0 RCX: 000000ff00000000
RDX: ffffc900043f7c20 RSI: ffff88805d988000 RDI: 00000000000004a8
RBP: ffffc900043f7c88 R08: 0000000000000001 R09: 0000000000000014
R10: ffff88805d98f8c0 R11: 0000000000000001 R12: ffff888025b61cc0
R13: 0000000000000000 R14: ffffea0001766201 R15: ff00000000801800
FS: 0000000000000000(0000) GS:ffff88802c200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000edc6be00 CR3: 000000000d97a000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@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