| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <6813b733.050a0220.53db9.0000.GAE@google.com> Date: Thu, 01 May 2025 11:02:27 -0700 From: syzbot <syzbot+5cf89626ecd9d0007691@...kaller.appspotmail.com> To: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, pasha.tatashin@...een.com, syzkaller-bugs@...glegroups.com Subject: [syzbot] [mm?] INFO: rcu detected stall in nsim_fib_event_work Hello, syzbot found the following issue on: HEAD commit: 5bc1018675ec Merge tag 'pci-v6.15-fixes-3' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15f130d4580000 kernel config: https://syzkaller.appspot.com/x/.config?x=9f5bd2a76d9d0b4e dashboard link: https://syzkaller.appspot.com/bug?extid=5cf89626ecd9d0007691 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=126c4374580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f130d4580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/33f182866e0b/disk-5bc10186.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/103760a3e862/vmlinux-5bc10186.xz kernel image: https://storage.googleapis.com/syzbot-assets/9954dc25ed1d/bzImage-5bc10186.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+5cf89626ecd9d0007691@...kaller.appspotmail.com bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P9/1:b..l rcu: (detected by 0, t=10503 jiffies, g=6869, q=616 ncpus=2) task:kworker/0:0 state:R running task stack:25496 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events nsim_fib_event_work Call Trace: <TASK> context_switch kernel/sched/core.c:5382 [inline] __schedule+0x116f/0x5de0 kernel/sched/core.c:6767 preempt_schedule_irq+0x51/0x90 kernel/sched/core.c:7090 irqentry_exit+0x36/0x90 kernel/entry/common.c:354 asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:702 RIP: 0010:__kasan_check_read+0x0/0x20 mm/kasan/shadow.c:30 Code: c3 cc cc cc cc 48 83 c4 60 48 c7 c7 90 22 a3 8d 5b 5d 41 5c e9 a1 c9 79 ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 48 8b 0c 24 89 f6 31 d2 e9 7f f0 ff ff 66 66 2e 0f 1f RSP: 0018:ffffc900000e78c8 EFLAGS: 00000293 RAX: 0000000000000000 RBX: ffff88801ed4d3d8 RCX: ffffffff822c44d1 RDX: ffff88801c6f4880 RSI: 0000000000000004 RDI: ffff88801ed4d3dc RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffff88801ed4d390 R13: ffff88801ed4d3dc R14: 0000000000000000 R15: dffffc0000000000 instrument_atomic_read include/linux/instrumented.h:68 [inline] atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline] __page_table_check_zero+0x260/0x5b0 mm/page_table_check.c:143 page_table_check_free include/linux/page_table_check.h:41 [inline] free_pages_prepare mm/page_alloc.c:1263 [inline] __free_frozen_pages+0x704/0xff0 mm/page_alloc.c:2725 discard_slab mm/slub.c:2730 [inline] __put_partials+0x16d/0x1c0 mm/slub.c:3199 qlink_free mm/kasan/quarantine.c:163 [inline] qlist_free_all+0x4e/0x120 mm/kasan/quarantine.c:179 kasan_quarantine_reduce+0x195/0x1e0 mm/kasan/quarantine.c:286 __kasan_kmalloc+0x8a/0xb0 mm/kasan/common.c:385 kmalloc_noprof include/linux/slab.h:905 [inline] kzalloc_noprof include/linux/slab.h:1039 [inline] nsim_fib6_rt_nh_add+0x4a/0x290 drivers/net/netdevsim/fib.c:500 nsim_fib6_rt_create drivers/net/netdevsim/fib.c:562 [inline] nsim_fib6_rt_insert drivers/net/netdevsim/fib.c:752 [inline] nsim_fib6_event drivers/net/netdevsim/fib.c:856 [inline] nsim_fib_event drivers/net/netdevsim/fib.c:889 [inline] nsim_fib_event_work+0x196a/0x2e80 drivers/net/netdevsim/fib.c:1493 process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238 process_scheduled_works kernel/workqueue.c:3319 [inline] worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400 kthread+0x3c2/0x780 kernel/kthread.c:464 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> net_ratelimit: 14203 callbacks suppressed bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) net_ratelimit: 16086 callbacks suppressed bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:12:9a:a3:e5:33:d9, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0) bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0) --- 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@...glegroups.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
Powered by blists - more mailing lists