[v6.1] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!

0 views
Skip to first unread message

syzbot

unread,
Mar 28, 2023, 6:33:44 PM3/28/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e8d7c1c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=390800ef8aeebc47
dashboard link: https://syzkaller.appspot.com/bug?extid=bab7a1cdf22616e99208
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f5022ccd560/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f8524664c631/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ad699b30c2c4/Image-e3a87a10.gz.xz

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

device veth1_macvtap left promiscuous mode
device veth0_macvtap left promiscuous mode
device veth1_vlan left promiscuous mode
device veth0_vlan left promiscuous mode
BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 0 PID: 13744 Comm: kworker/u4:17 Not tainted 6.1.21-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: netns cleanup_net
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3779 [inline]
validate_chain kernel/locking/lockdep.c:3800 [inline]
__lock_acquire+0x1b8c/0x764c kernel/locking/lockdep.c:5056
lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669
_raw_spin_lock_nested+0x5c/0x78 kernel/locking/spinlock.c:378
raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
raw_spin_rq_lock kernel/sched/sched.h:1354 [inline]
rq_lock kernel/sched/sched.h:1644 [inline]
ttwu_queue kernel/sched/core.c:3896 [inline]
try_to_wake_up+0x4c8/0xe60 kernel/sched/core.c:4221
wake_up_process+0x18/0x24 kernel/sched/core.c:4355
wake_up_worker kernel/workqueue.c:856 [inline]
insert_work+0x2ac/0x384 kernel/workqueue.c:1366
__queue_work+0xd48/0x136c kernel/workqueue.c:1517
queue_work_on+0xc0/0x16c kernel/workqueue.c:1545
queue_work include/linux/workqueue.h:503 [inline]
synchronize_rcu_expedited_queue_work kernel/rcu/tree_exp.h:518 [inline]
synchronize_rcu_expedited+0x514/0x768 kernel/rcu/tree_exp.h:958
synchronize_net net/core/dev.c:10743 [inline]
netdev_rx_handler_unregister+0xa4/0x10c net/core/dev.c:5237
team_port_del+0x38c/0xadc drivers/net/team/team.c:1351
team_del_slave+0x44/0x1a8 drivers/net/team/team.c:1999
team_device_event+0x260/0x40c drivers/net/team/team.c:3022
notifier_call_chain kernel/notifier.c:87 [inline]
raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:455
call_netdevice_notifiers_info net/core/dev.c:1945 [inline]
call_netdevice_notifiers_extack net/core/dev.c:1983 [inline]
call_netdevice_notifiers net/core/dev.c:1997 [inline]
unregister_netdevice_many+0xe6c/0x1818 net/core/dev.c:10841
default_device_exit_batch+0x6c0/0x73c net/core/dev.c:11335
ops_exit_list net/core/net_namespace.c:174 [inline]
cleanup_net+0x5dc/0x994 net/core/net_namespace.c:601
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2289
worker_thread+0x8e4/0xfec kernel/workqueue.c:2436
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
team0 (unregistering): Port device team_slave_1 removed
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): (slave bond_slave_1): Releasing backup interface
bond0 (unregistering): (slave bond_slave_0): Releasing backup interface
bond0 (unregistering): Released all slaves
wlan0: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan0: Creating new IBSS network, BSSID 50:50:50:50:50:50
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device
vhci_hcd: stop threads
vhci_hcd: release socket
vhci_hcd: disconnect device


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

syzbot

unread,
Jul 17, 2023, 4:29:56 AM7/17/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 61fd484b2cf6 Linux 6.1.38
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11abe742a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3b4be05fdc3de90a
dashboard link: https://syzkaller.appspot.com/bug?extid=bab7a1cdf22616e99208
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12bad0aaa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12951456a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/710437ee8127/disk-61fd484b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a61ff183628e/vmlinux-61fd484b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/522fb55f8194/Image-61fd484b.gz.xz

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

BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
turning off the locking correctness validator.
CPU: 1 PID: 8521 Comm: syz-executor924 Not tainted 6.1.38-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3779 [inline]
validate_chain kernel/locking/lockdep.c:3800 [inline]
__lock_acquire+0x1b8c/0x764c kernel/locking/lockdep.c:5056
lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669
fs_reclaim_acquire+0xbc/0x12c mm/page_alloc.c:4700
might_alloc include/linux/sched/mm.h:271 [inline]
slab_pre_alloc_hook mm/slab.h:710 [inline]
slab_alloc_node mm/slub.c:3318 [inline]
__kmem_cache_alloc_node+0x58/0x388 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:954 [inline]
__kmalloc+0xc4/0x1c4 mm/slab_common.c:968
kmalloc_array include/linux/slab.h:605 [inline]
kcalloc include/linux/slab.h:636 [inline]
__team_options_register drivers/net/team/team.c:261 [inline]
team_options_register+0x48/0x940 drivers/net/team/team.c:341
ab_init+0x2c/0x3c drivers/net/team/team_mode_activebackup.c:105
__team_change_mode+0x284/0x4a0 drivers/net/team/team.c:578
team_change_mode drivers/net/team/team.c:612 [inline]
team_mode_option_set+0x324/0x390 drivers/net/team/team.c:1388
team_option_set drivers/net/team/team.c:374 [inline]
team_nl_cmd_options_set+0x7e0/0xdec drivers/net/team/team.c:2663
genl_family_rcv_msg_doit net/netlink/genetlink.c:756 [inline]
genl_family_rcv_msg net/netlink/genetlink.c:833 [inline]
genl_rcv_msg+0x948/0xc2c net/netlink/genetlink.c:850
netlink_rcv_skb+0x20c/0x3b8 net/netlink/af_netlink.c:2524
genl_rcv+0x38/0x50 net/netlink/genetlink.c:861
netlink_unicast_kernel net/netlink/af_netlink.c:1328 [inline]
netlink_unicast+0x660/0x8d4 net/netlink/af_netlink.c:1354
netlink_sendmsg+0x834/0xb18 net/netlink/af_netlink.c:1902
sock_sendmsg_nosec net/socket.c:716 [inline]
sock_sendmsg net/socket.c:736 [inline]
____sys_sendmsg+0x558/0x844 net/socket.c:2482
___sys_sendmsg net/socket.c:2536 [inline]
__sys_sendmsg+0x26c/0x33c net/socket.c:2565
__do_sys_sendmsg net/socket.c:2574 [inline]
__se_sys_sendmsg net/socket.c:2572 [inline]
__arm64_sys_sendmsg+0x80/0x94 net/socket.c:2572
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
team3452: Mode changed to "activebackup"


---
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.
Reply all
Reply to author
Forward
0 new messages