syzbot


WARNING in retire_sysctl_set

Status: auto-closed as invalid on 2022/06/25 23:00
Reported-by: syzbot+4d1fdc2649adecca417d@syzkaller.appspotmail.com
First crash: 761d, last: 761d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in retire_sysctl_set fs 1 501d 501d 0/26 closed as invalid on 2023/02/17 17:35

Sample crash report:
8021q: adding VLAN 0 to HW filter on device batadv0
IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready
------------[ cut here ]------------
8021q: adding VLAN 0 to HW filter on device batadv0
WARNING: CPU: 0 PID: 7387 at fs/proc/proc_sysctl.c:1693 retire_sysctl_set.cold+0x11/0x18 fs/proc/proc_sysctl.c:1693
IPv6: ADDRCONF(NETDEV_UP): veth0_virt_wifi: link is not ready
Kernel panic - not syncing: panic_on_warn set ...

IPv6: ADDRCONF(NETDEV_UP): veth1_virt_wifi: link is not ready
CPU: 0 PID: 7387 Comm: kworker/u4:1 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 panic+0x26a/0x50e kernel/panic.c:186
IPv6: ADDRCONF(NETDEV_UP): veth0_vlan: link is not ready
IPv6: ADDRCONF(NETDEV_UP): vlan0: link is not ready
 __warn.cold+0x20/0x5a kernel/panic.c:541
IPv6: ADDRCONF(NETDEV_UP): vlan1: link is not ready
 report_bug+0x262/0x2b0 lib/bug.c:183
IPv6: ADDRCONF(NETDEV_UP): veth1_vlan: link is not ready
 fixup_bug arch/x86/kernel/traps.c:178 [inline]
 fixup_bug arch/x86/kernel/traps.c:173 [inline]
 do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
device veth0_vlan entered promiscuous mode
device veth1_vlan entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvlan0: link is not ready
 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:retire_sysctl_set.cold+0x11/0x18 fs/proc/proc_sysctl.c:1693
IPv6: ADDRCONF(NETDEV_UP): macvlan1: link is not ready
Code: c7 c7 40 42 77 88 e8 53 c6 fe ff 48 8b 3c 24 e8 3f 47 ce f9 e9 48 ff ff ff e8 d5 94 6d f9 48 c7 c7 80 42 77 88 e8 34 c6 fe ff <0f> 0b e9 bd a5 ce f9 e8 bd 94 6d f9 48 c7 c7 00 5e 77 88 c6 05 18
IPv6: ADDRCONF(NETDEV_UP): veth0_macvtap: link is not ready
RSP: 0018:ffff888074407c18 EFLAGS: 00010282
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
RAX: 0000000000000024 RBX: ffff88807da39d98 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed100e880f75
RBP: ffffffff87ccbf60 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffffffff8b079060
R13: ffff888074407cc8 R14: dffffc0000000000 R15: fffffbfff160f20f
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153
device veth1_macvtap entered promiscuous mode
 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:554
IPv6: ADDRCONF(NETDEV_UP): macsec0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
 process_one_work+0x864/0x1570 kernel/workqueue.c:2153
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
 kthread+0x33f/0x460 kernel/kthread.c:259
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/02/25 23:00 linux-4.19.y 3f8a27f9e27b 45a13a73 .config console log report info ci2-linux-4-19 WARNING in retire_sysctl_set
* Struck through repros no longer work on HEAD.