[moderation] [kernel?] WARNING: proc registration bug in unregister_irq_proc (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2d3090a8aeb5 Merge tag 'v7.1-p5' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ae60ae580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4e4d2284f2ffa41
dashboard link: https://syzkaller.appspot.com/bug?extid=d5e7b3989f1ddbf72a57
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: i386
CC: [linux-...@vger.kernel.org tg...@kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-2d3090a8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/728490f77062/vmlinux-2d3090a8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0950607802a2/bzImage-2d3090a8.xz

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

genirq: Flags mismatch irq 31. 00200000 (eth1-tx-0) vs. 00200000 (comedi_parport)
------------[ cut here ]------------
remove_proc_entry: removing non-empty directory 'irq/30', leaking at least 'eth1-rx-0'
WARNING: fs/proc/generic.c:742 at remove_proc_entry+0x4b1/0x5b0 fs/proc/generic.c:742, CPU#1: syz.6.5720/28084
Modules linked in:
CPU: 1 UID: 0 PID: 28084 Comm: syz.6.5720 Tainted: G L syzkaller #0 PREEMPT(full)
Tainted: [L]=SOFTLOCKUP
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:remove_proc_entry+0x4c5/0x5b0 fs/proc/generic.c:742
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 b3 00 00 00 48 8d 3d 8f 7a 28 0e 48 8b 93 d0 00 00 00 4d 89 f0 4c 89 e9 48 c7 c6 80 6b c9 8b <67> 48 0f b9 3a e9 5a fe ff ff e8 1c eb 52 ff 48 8d 7d 18 48 b8 00
RSP: 0000:ffffc9000d31e880 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff88801cb48500 RCX: ffff88804b6cf4dc
RDX: ffff88801cb485dc RSI: ffffffff8bc96b80 RDI: ffffffff90dd8cb0
RBP: ffff88804b6cf4b8 R08: ffff888053198fdc R09: ffffed10096d9e83
R10: ffff88804b6cf41b R11: 0000000000000000 R12: ffff88804b6cf400
R13: ffff88804b6cf4dc R14: ffff888053198fdc R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff88809728e000(0063) knlGS:00000000f53ebb40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00000000f71f7810 CR3: 000000006faed000 CR4: 0000000000352ef0
Call Trace:
<TASK>
unregister_irq_proc+0x200/0x2a0 kernel/irq/proc.c:405
free_desc+0x8a/0x190 kernel/irq/irqdesc.c:474
irq_free_descs kernel/irq/irqdesc.c:870 [inline]
irq_free_descs+0x84/0xc0 kernel/irq/irqdesc.c:861
irq_domain_free_irqs+0x46a/0x5c0 kernel/irq/irqdomain.c:1914
__msi_domain_free_irqs kernel/irq/msi.c:1619 [inline]
msi_domain_free_locked.part.0+0x524/0x6b0 kernel/irq/msi.c:1645
msi_domain_free_locked kernel/irq/msi.c:1632 [inline]
msi_domain_free_irqs_range_locked kernel/irq/msi.c:1668 [inline]
msi_domain_free_irqs_all_locked+0x11d/0x170 kernel/irq/msi.c:1701
pci_msi_teardown_msi_irqs+0xb3/0xd0 drivers/pci/msi/irqdomain.c:28
pci_free_msi_irqs+0x1f/0xa0 drivers/pci/msi/msi.c:925
pci_disable_msix drivers/pci/msi/api.c:200 [inline]
pci_disable_msix+0xcf/0x110 drivers/pci/msi/api.c:193
e1000e_reset_interrupt_capability drivers/net/ethernet/intel/e1000e/netdev.c:2029 [inline]
e1000_request_irq+0x473/0xdc0 drivers/net/ethernet/intel/e1000e/netdev.c:2163
e1000e_open+0x471/0x1800 drivers/net/ethernet/intel/e1000e/netdev.c:4675
__dev_open+0x3ad/0x8f0 net/core/dev.c:1702
__dev_change_flags+0x596/0x850 net/core/dev.c:9758
netif_change_flags+0x8d/0x160 net/core/dev.c:9821
do_setlink.isra.0+0x1ac4/0x3e60 net/core/rtnetlink.c:3181
rtnl_group_changelink net/core/rtnetlink.c:3814 [inline]
__rtnl_newlink net/core/rtnetlink.c:3982 [inline]
rtnl_newlink+0x1b7e/0x2380 net/core/rtnetlink.c:4110
rtnetlink_rcv_msg+0x95e/0xe90 net/core/rtnetlink.c:6997
netlink_rcv_skb+0x159/0x420 net/netlink/af_netlink.c:2555
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x585/0x850 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x8b0/0xda0 net/netlink/af_netlink.c:1899
sock_sendmsg_nosec net/socket.c:787 [inline]
__sock_sendmsg net/socket.c:802 [inline]
____sys_sendmsg+0x9e1/0xb70 net/socket.c:2698
___sys_sendmsg+0x190/0x1e0 net/socket.c:2752
__sys_sendmsg+0x170/0x220 net/socket.c:2784
do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]
__do_fast_syscall_32+0xe7/0x970 arch/x86/entry/syscall_32.c:307
do_fast_syscall_32+0x32/0x70 arch/x86/entry/syscall_32.c:332
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf703ef7c
Code: d2 74 05 c1 e8 0c 89 02 8b 5d fc 31 c0 c9 c3 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 2e 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 58 b8
RSP: 002b:00000000f53eb50c EFLAGS: 00000292 ORIG_RAX: 0000000000000172
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000080000140
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
----------------
Code disassembly (best guess):
0: fa cli
1: 48 c1 ea 03 shr $0x3,%rdx
5: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
9: 0f 85 b3 00 00 00 jne 0xc2
f: 48 8d 3d 8f 7a 28 0e lea 0xe287a8f(%rip),%rdi # 0xe287aa5
16: 48 8b 93 d0 00 00 00 mov 0xd0(%rbx),%rdx
1d: 4d 89 f0 mov %r14,%r8
20: 4c 89 e9 mov %r13,%rcx
23: 48 c7 c6 80 6b c9 8b mov $0xffffffff8bc96b80,%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: e9 5a fe ff ff jmp 0xfffffe8e
34: e8 1c eb 52 ff call 0xff52eb55
39: 48 8d 7d 18 lea 0x18(%rbp),%rdi
3d: 48 rex.W
3e: b8 .byte 0xb8


---
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