[moderation] [fs?] general protection fault in ib_free_port_attrs

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 293e38ff4e4c net: lan743x: Restore SGMII CTRL register on ..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=16d6e9f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c3f0e807ec5d1268
dashboard link: https://syzkaller.appspot.com/bug?extid=9151b8478e75130c571c
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
CC: [da...@kernel.org gre...@linuxfoundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org net...@vger.kernel.org raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1aa64db2444/disk-293e38ff.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9a5c7599e740/vmlinux-293e38ff.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1bac674c6902/bzImage-293e38ff.xz

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

Oops: general protection fault, probably for non-canonical address 0xe5ee6a4caecd2e4c: 0000 [#1] SMP KASAN PTI
KASAN: maybe wild-memory-access in range [0x2f73726576697260-0x2f73726576697267]
CPU: 1 UID: 0 PID: 13 Comm: kworker/u8:1 Not tainted 6.15.0-rc6-syzkaller-00182-g293e38ff4e4c #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: netns cleanup_net
RIP: 0010:sysfs_remove_group+0x47/0x2c0 fs/sysfs/group.c:310
Code: ff df e8 5c 69 63 ff 4d 8d 77 30 4c 89 f0 48 c1 e8 03 80 3c 28 00 74 08 4c 89 f7 e8 93 62 c5 ff 4d 8b 36 49 89 dc 49 c1 ec 03 <41> 80 3c 2c 00 74 08 48 89 df e8 7a 62 c5 ff 48 8b 33 48 85 f6 74
RSP: 0018:ffffc90000127830 EFLAGS: 00010203
RAX: 1ffff11005b4b706 RBX: 2f73726576697264 RCX: ffff88801c6d0000
RDX: 0000000000000000 RSI: 2f73726576697264 RDI: ffff88802da5b800
RBP: dffffc0000000000 R08: ffff8880266af963 R09: 1ffff11004cd5f2c
R10: dffffc0000000000 R11: ffffed1004cd5f2d R12: 05ee6e4caecd2e4c
R13: dffffc0000000000 R14: ffff8880266af960 R15: ffff88802da5b800
FS: 0000000000000000(0000) GS:ffff8881261c7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9637046e9c CR3: 000000007c946000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
sysfs_remove_groups+0x54/0xb0 fs/sysfs/group.c:346
__kobject_del+0x84/0x300 lib/kobject.c:595
kobject_del+0x45/0x60 lib/kobject.c:627
destroy_port drivers/infiniband/core/sysfs.c:1279 [inline]
ib_free_port_attrs+0x289/0x3b0 drivers/infiniband/core/sysfs.c:1408
remove_one_compat_dev drivers/infiniband/core/device.c:1001 [inline]
rdma_dev_exit_net+0x1d8/0x340 drivers/infiniband/core/device.c:1139
ops_exit_list net/core/net_namespace.c:172 [inline]
cleanup_net+0x717/0xbd0 net/core/net_namespace.c:654
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xade/0x17a0 kernel/workqueue.c:3319
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3400
kthread+0x711/0x8a0 kernel/kthread.c:464
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:sysfs_remove_group+0x47/0x2c0 fs/sysfs/group.c:310
Code: ff df e8 5c 69 63 ff 4d 8d 77 30 4c 89 f0 48 c1 e8 03 80 3c 28 00 74 08 4c 89 f7 e8 93 62 c5 ff 4d 8b 36 49 89 dc 49 c1 ec 03 <41> 80 3c 2c 00 74 08 48 89 df e8 7a 62 c5 ff 48 8b 33 48 85 f6 74
RSP: 0018:ffffc90000127830 EFLAGS: 00010203
RAX: 1ffff11005b4b706 RBX: 2f73726576697264 RCX: ffff88801c6d0000
RDX: 0000000000000000 RSI: 2f73726576697264 RDI: ffff88802da5b800
RBP: dffffc0000000000 R08: ffff8880266af963 R09: 1ffff11004cd5f2c
R10: dffffc0000000000 R11: ffffed1004cd5f2d R12: 05ee6e4caecd2e4c
R13: dffffc0000000000 R14: ffff8880266af960 R15: ffff88802da5b800
FS: 0000000000000000(0000) GS:ffff8881261c7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000558a572b0000 CR3: 0000000032c66000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: df e8 fucomip %st(0),%st
2: 5c pop %rsp
3: 69 63 ff 4d 8d 77 30 imul $0x30778d4d,-0x1(%rbx),%esp
a: 4c 89 f0 mov %r14,%rax
d: 48 c1 e8 03 shr $0x3,%rax
11: 80 3c 28 00 cmpb $0x0,(%rax,%rbp,1)
15: 74 08 je 0x1f
17: 4c 89 f7 mov %r14,%rdi
1a: e8 93 62 c5 ff call 0xffc562b2
1f: 4d 8b 36 mov (%r14),%r14
22: 49 89 dc mov %rbx,%r12
25: 49 c1 ec 03 shr $0x3,%r12
* 29: 41 80 3c 2c 00 cmpb $0x0,(%r12,%rbp,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 df mov %rbx,%rdi
33: e8 7a 62 c5 ff call 0xffc562b2
38: 48 8b 33 mov (%rbx),%rsi
3b: 48 85 f6 test %rsi,%rsi
3e: 74 .byte 0x74


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.