[v6.1] WARNING in __mod_timer

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5cd595e23c1 Linux 6.1.83
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fa2af9180000
kernel config: https://syzkaller.appspot.com/x/.config?x=99d0cbbc2b2c7cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=12d910b559660fec2af0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e4bb76180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163706e5180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/607b4730a2cc/disk-e5cd595e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/265e84c69ac5/vmlinux-e5cd595e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/af893c46019b/bzImage-e5cd595e.xz

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

------------[ cut here ]------------
raw_local_irq_restore() called with IRQs enabled
WARNING: CPU: 0 PID: 15 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Modules linked in:

CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.83-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:warn_bogus_irq_restore+0x1d/0x20 kernel/locking/irqflag-debug.c:10
Code: 24 48 c7 c7 80 bb ea 8a e8 6c f5 fd ff 80 3d af 86 d5 03 00 74 01 c3 c6 05 a5 86 d5 03 01 48 c7 c7 e0 e5 eb 8a e8 23 94 c8 f6 <0f> 0b c3 41 56 53 48 83 ec 10 65 48 8b 04 25 28 00 00 00 48 89 44
RSP: 0018:ffffc900001475f8 EFLAGS: 00010246

RAX: 9946aff1f597ec00 RBX: 1ffff92000028ec4 RCX: ffff88813feabb80
RDX: 0000000080000102 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000147690 R08: ffffffff81527eae R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff92000028ec0 R14: ffffc90000147620 R15: 0000000000000046
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb398666110 CR3: 000000002245c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
_raw_spin_unlock_irqrestore+0x118/0x130 kernel/locking/spinlock.c:194
__mod_timer+0x956/0xee0 kernel/time/timer.c:1118
queue_delayed_work_on+0x156/0x250 kernel/workqueue.c:1704
queue_delayed_work include/linux/workqueue.h:527 [inline]
srcu_funnel_gp_start kernel/rcu/srcutree.c:951 [inline]
srcu_gp_start_if_needed+0xce5/0x1080 kernel/rcu/srcutree.c:1151
rcu_do_batch kernel/rcu/tree.c:2296 [inline]
rcu_core+0xad4/0x17e0 kernel/rcu/tree.c:2556
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x52c/0xa30 kernel/smpboot.c:164
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</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 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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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

[syzbot]

syzbot suspects this issue was fixed by commit:

commit a44770fed86515eedb5a7c00b787f847ebb134a5
Author: Jakub Sitnicki <ja...@cloudflare.com>
Date: Tue Apr 2 10:46:21 2024 +0000

bpf, sockmap: Prevent lock inversion deadlock in map delete elem

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166b8440980000
start commit: e5cd595e23c1 Linux 6.1.83
git tree: linux-6.1.y

kernel config: https://syzkaller.appspot.com/x/.config?x=99d0cbbc2b2c7cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=12d910b559660fec2af0

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e4bb76180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163706e5180000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: bpf, sockmap: Prevent lock inversion deadlock in map delete elem

For information about bisection process see: https://goo.gl/tpsmEJ#bisection