* [syzbot] [net?] WARNING in ipmr_rules_exit (2)
@ 2025-06-03 15:31 syzbot
2025-06-03 15:36 ` Paolo Abeni
0 siblings, 1 reply; 2+ messages in thread
From: syzbot @ 2025-06-03 15:31 UTC (permalink / raw)
To: davem, dsahern, edumazet, horms, kuba, linux-kernel, linux-usb,
netdev, pabeni, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 342e4955a1f1 usb: usbtmc: Fix timeout value in get_stb
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=135a19f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cc73a376913a3005
dashboard link: https://syzkaller.appspot.com/bug?extid=a25af2d6c990a65eca95
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3d4486b9330e/disk-342e4955.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b0b416348409/vmlinux-342e4955.xz
kernel image: https://storage.googleapis.com/syzbot-assets/053a330bcf59/bzImage-342e4955.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a25af2d6c990a65eca95@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 13600 at net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440 [inline]
WARNING: CPU: 0 PID: 13600 at net/ipv4/ipmr.c:440 ipmr_rules_exit+0x13a/0x1c0 net/ipv4/ipmr.c:361
Modules linked in:
CPU: 0 UID: 0 PID: 13600 Comm: syz-executor Not tainted 6.15.0-rc6-syzkaller-00166-g342e4955a1f1 #0 PREEMPT(voluntary)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ipmr_free_table net/ipv4/ipmr.c:440 [inline]
RIP: 0010:ipmr_rules_exit+0x13a/0x1c0 net/ipv4/ipmr.c:361
Code: ff df 48 c1 ea 03 80 3c 02 00 75 7c 48 c7 85 58 09 00 00 00 00 00 00 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc e8 d7 79 16 fb 90 <0f> 0b 90 eb 93 e8 cc 79 16 fb 0f b6 1d 73 37 05 04 31 ff 89 de e8
RSP: 0018:ffffc90014e2fc10 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88812c1dc000 RCX: ffffffff8665f0fd
RDX: ffff8881222c9d40 RSI: ffffffff8665f169 RDI: 0000000000000005
RBP: ffff88812ea70000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
R13: ffff88812ea70958 R14: ffff88812ea70000 R15: fffffbfff148e04c
FS: 000055558afcb500(0000) GS:ffff8882691c2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc07c1d33d0 CR3: 000000014620e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ipmr_net_exit_batch+0x53/0xa0 net/ipv4/ipmr.c:3160
ops_exit_list+0x128/0x180 net/core/net_namespace.c:177
setup_net+0x4e8/0x850 net/core/net_namespace.c:396
copy_net_ns+0x2a6/0x5f0 net/core/net_namespace.c:518
create_new_namespaces+0x3ea/0xad0 kernel/nsproxy.c:110
unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228
ksys_unshare+0x45b/0xa40 kernel/fork.c:3375
__do_sys_unshare kernel/fork.c:3446 [inline]
__se_sys_unshare kernel/fork.c:3444 [inline]
__x64_sys_unshare+0x31/0x40 kernel/fork.c:3444
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f31d7a50167
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe9bbc8f18 EFLAGS: 00000206
ORIG_RAX: 0000000000000110
RAX: ffffffffffffffda RBX: 00007f31d7c75f40 RCX: 00007f31d7a50167
RDX: 0000000000000005 RSI: 00007ffe9bbc8de0 RDI: 0000000040000000
RBP: 00007f31d7c76738 R08: 00007f31d87a7d60 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000008
R13: 0000000000000003 R14: 0000000000000009 R15: 0000000000000000
</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 syzkaller@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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [syzbot] [net?] WARNING in ipmr_rules_exit (2)
2025-06-03 15:31 [syzbot] [net?] WARNING in ipmr_rules_exit (2) syzbot
@ 2025-06-03 15:36 ` Paolo Abeni
0 siblings, 0 replies; 2+ messages in thread
From: Paolo Abeni @ 2025-06-03 15:36 UTC (permalink / raw)
To: syzbot, davem, dsahern, edumazet, horms, kuba, linux-kernel,
linux-usb, netdev, syzkaller-bugs
On 6/3/25 5:31 PM, syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit: 342e4955a1f1 usb: usbtmc: Fix timeout value in get_stb
> git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> console output: https://syzkaller.appspot.com/x/log.txt?x=135a19f4580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cc73a376913a3005
> dashboard link: https://syzkaller.appspot.com/bug?extid=a25af2d6c990a65eca95
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/3d4486b9330e/disk-342e4955.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/b0b416348409/vmlinux-342e4955.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/053a330bcf59/bzImage-342e4955.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a25af2d6c990a65eca95@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 13600 at net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440 [inline]
> WARNING: CPU: 0 PID: 13600 at net/ipv4/ipmr.c:440 ipmr_rules_exit+0x13a/0x1c0 net/ipv4/ipmr.c:361
> Modules linked in:
>
> CPU: 0 UID: 0 PID: 13600 Comm: syz-executor Not tainted 6.15.0-rc6-syzkaller-00166-g342e4955a1f1 #0 PREEMPT(voluntary)
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
> RIP: 0010:ipmr_free_table net/ipv4/ipmr.c:440 [inline]
> RIP: 0010:ipmr_rules_exit+0x13a/0x1c0 net/ipv4/ipmr.c:361
> Code: ff df 48 c1 ea 03 80 3c 02 00 75 7c 48 c7 85 58 09 00 00 00 00 00 00 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc e8 d7 79 16 fb 90 <0f> 0b 90 eb 93 e8 cc 79 16 fb 0f b6 1d 73 37 05 04 31 ff 89 de e8
> RSP: 0018:ffffc90014e2fc10 EFLAGS: 00010293
>
> RAX: 0000000000000000 RBX: ffff88812c1dc000 RCX: ffffffff8665f0fd
> RDX: ffff8881222c9d40 RSI: ffffffff8665f169 RDI: 0000000000000005
> RBP: ffff88812ea70000 R08: 0000000000000005 R09: 0000000000000000
> R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
> R13: ffff88812ea70958 R14: ffff88812ea70000 R15: fffffbfff148e04c
> FS: 000055558afcb500(0000) GS:ffff8882691c2000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007fc07c1d33d0 CR3: 000000014620e000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> ipmr_net_exit_batch+0x53/0xa0 net/ipv4/ipmr.c:3160
> ops_exit_list+0x128/0x180 net/core/net_namespace.c:177
> setup_net+0x4e8/0x850 net/core/net_namespace.c:396
> copy_net_ns+0x2a6/0x5f0 net/core/net_namespace.c:518
> create_new_namespaces+0x3ea/0xad0 kernel/nsproxy.c:110
> unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228
> ksys_unshare+0x45b/0xa40 kernel/fork.c:3375
> __do_sys_unshare kernel/fork.c:3446 [inline]
> __se_sys_unshare kernel/fork.c:3444 [inline]
> __x64_sys_unshare+0x31/0x40 kernel/fork.c:3444
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f31d7a50167
> Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffe9bbc8f18 EFLAGS: 00000206
> ORIG_RAX: 0000000000000110
> RAX: ffffffffffffffda RBX: 00007f31d7c75f40 RCX: 00007f31d7a50167
> RDX: 0000000000000005 RSI: 00007ffe9bbc8de0 RDI: 0000000040000000
> RBP: 00007f31d7c76738 R08: 00007f31d87a7d60 R09: 0000000000000000
> R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000008
> R13: 0000000000000003 R14: 0000000000000009 R15: 0000000000000000
> </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 syzkaller@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
#syz fix: mr: consolidate the ipmr_can_free_table() checks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-06-03 15:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-03 15:31 [syzbot] [net?] WARNING in ipmr_rules_exit (2) syzbot
2025-06-03 15:36 ` Paolo Abeni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).