syzbot

=============================
[ BUG: Invalid wait context ]
6.12.0-syzkaller-05480-gfcc79e1714e8 #0 Not tainted
-----------------------------
syz.1.233/6687 is trying to lock:
ffffffff8e39fbd8 (stack_list_lock){-.-.}-{3:3}, at: add_stack_record_to_list mm/page_owner.c:182 [inline]
ffffffff8e39fbd8 (stack_list_lock){-.-.}-{3:3}, at: inc_stack_record_count mm/page_owner.c:214 [inline]
ffffffff8e39fbd8 (stack_list_lock){-.-.}-{3:3}, at: __set_page_owner+0x3ea/0x560 mm/page_owner.c:329
other info that might help us debug this:
context-{2:2}
1 lock held by syz.1.233/6687:
 #0: ffff88807a2cf110 (&u->iolock){+.+.}-{4:4}, at: __unix_dgram_recvmsg+0x267/0xe50 net/unix/af_unix.c:2432
stack backtrace:
CPU: 1 UID: 0 PID: 6687 Comm: syz.1.233 Not tainted 6.12.0-syzkaller-05480-gfcc79e1714e8 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_lock_invalid_wait_context kernel/locking/lockdep.c:4826 [inline]
 check_wait_context kernel/locking/lockdep.c:4898 [inline]
 __lock_acquire+0x878/0x3c40 kernel/locking/lockdep.c:5176
 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1038 [inline]
 __sysvec_apic_timer_interrupt+0x10f/0x400 arch/x86/kernel/apic/apic.c:1055
 __unix_dgram_recvmsg+0x1d1/0xe50 net/unix/af_unix.c:2435