[v5.15] BUG: MAX_LOCKDEP_CHAINS too low!
13 views
Skip to first unread message
syzbot
Mar 7, 2023, 11:44:42 AM3/7/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127c945cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=77595558bad304ba6a00
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/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+775955...@syzkaller.appspotmail.com
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 9 Comm: kworker/u4:0 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: phy324 ieee80211_iface_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3734 [inline]
validate_chain kernel/locking/lockdep.c:3755 [inline]
__lock_acquire+0x1b68/0x7620 kernel/locking/lockdep.c:5011
lock_acquire+0x2b8/0x894 kernel/locking/lockdep.c:5622
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0xb0/0x10c kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:363 [inline]
__d_instantiate+0x134/0x6b4 fs/dcache.c:1975
d_instantiate+0x74/0xa0 fs/dcache.c:2010
debugfs_create_dir+0x1f0/0x420 fs/debugfs/inode.c:581
ieee80211_sta_debugfs_add+0x114/0x678 net/mac80211/debugfs_sta.c:1016
sta_info_insert_finish net/mac80211/sta_info.c:683 [inline]
sta_info_insert_rcu+0x15b8/0x1c84 net/mac80211/sta_info.c:731
ieee80211_ibss_finish_sta+0x1e8/0x2d8 net/mac80211/ibss.c:589
ieee80211_ibss_work+0x1f8/0x1210 net/mac80211/ibss.c:1702
ieee80211_iface_work+0x9d0/0xa80 net/mac80211/iface.c:1517
process_one_work+0x82c/0x1478 kernel/workqueue.c:2306
worker_thread+0x910/0x1034 kernel/workqueue.c:2453
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 <unknown>:870
wlan1: send auth to 08:02:11:00:00:00 (try 2/3)
wlan1: authentication with 08:02:11:00:00:00 timed out
wlan1: send auth to 08:02:11:00:00:00 (try 3/3)
wlan1: send auth to 08:02:11:00:00:00 (try 2/3)
wlan1: send auth to 08:02:11:00:00:00 (try 3/3)
wlan1: authentication with 08:02:11:00:00:00 timed out
---
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 found the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127c945cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=77595558bad304ba6a00
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/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+775955...@syzkaller.appspotmail.com
wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50
wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 9 Comm: kworker/u4:0 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: phy324 ieee80211_iface_work
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3734 [inline]
validate_chain kernel/locking/lockdep.c:3755 [inline]
__lock_acquire+0x1b68/0x7620 kernel/locking/lockdep.c:5011
lock_acquire+0x2b8/0x894 kernel/locking/lockdep.c:5622
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0xb0/0x10c kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:363 [inline]
__d_instantiate+0x134/0x6b4 fs/dcache.c:1975
d_instantiate+0x74/0xa0 fs/dcache.c:2010
debugfs_create_dir+0x1f0/0x420 fs/debugfs/inode.c:581
ieee80211_sta_debugfs_add+0x114/0x678 net/mac80211/debugfs_sta.c:1016
sta_info_insert_finish net/mac80211/sta_info.c:683 [inline]
sta_info_insert_rcu+0x15b8/0x1c84 net/mac80211/sta_info.c:731
ieee80211_ibss_finish_sta+0x1e8/0x2d8 net/mac80211/ibss.c:589
ieee80211_ibss_work+0x1f8/0x1210 net/mac80211/ibss.c:1702
ieee80211_iface_work+0x9d0/0xa80 net/mac80211/iface.c:1517
process_one_work+0x82c/0x1478 kernel/workqueue.c:2306
worker_thread+0x910/0x1034 kernel/workqueue.c:2453
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 <unknown>:870
wlan1: send auth to 08:02:11:00:00:00 (try 2/3)
wlan1: authentication with 08:02:11:00:00:00 timed out
wlan1: send auth to 08:02:11:00:00:00 (try 3/3)
wlan1: send auth to 08:02:11:00:00:00 (try 2/3)
wlan1: send auth to 08:02:11:00:00:00 (try 3/3)
wlan1: authentication with 08:02:11:00:00:00 timed out
---
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
Mar 7, 2023, 1:13:48 PM3/7/23
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11df899cc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=650737f7e9682672
dashboard link: https://syzkaller.appspot.com/bug?extid=7a44bac76a5b55f56fcd
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/f10713d1fd0f/disk-42616e0f.raw.xz
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: hci8 hci_tx_work
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/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3778 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
validate_chain kernel/locking/lockdep.c:3799 [inline]
__lock_acquire+0x1b8c/0x764c kernel/locking/lockdep.c:5055
lock_acquire+0x2f8/0x8dc kernel/locking/lockdep.c:5668
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x6c/0xb4 kernel/locking/spinlock.c:162
skb_dequeue+0x38/0x144 net/core/skbuff.c:3401
hci_sched_acl_pkt net/bluetooth/hci_core.c:3587 [inline]
hci_sched_acl net/bluetooth/hci_core.c:3677 [inline]
hci_tx_work+0xb64/0x1850 net/bluetooth/hci_core.c:3776
process_one_work+0x848/0x16b4 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
Bluetooth: hci8: command 0x0409 tx timeout
Bluetooth: hci8: command 0x0419 tx timeout
syzbot
Mar 8, 2023, 9:11:52 AM3/8/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17dacdcac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1513db7ac80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+775955...@syzkaller.appspotmail.com
___slab_alloc+0x1fc/0xdbc mm/slub.c:2930
__slab_alloc mm/slub.c:3095 [inline]
slab_alloc_node mm/slub.c:3186 [inline]
slab_alloc mm/slub.c:3228 [inline]
kmem_cache_alloc+0x340/0x4c4 mm/slub.c:3233
skb_clone+0x180/0x304 net/core/skbuff.c:1523
dev_queue_xmit_nit+0x1fc/0x944 net/core/dev.c:2290
xmit_one net/core/dev.c:3585 [inline]
dev_hard_start_xmit+0x124/0xc10 net/core/dev.c:3606
__dev_queue_xmit+0x1430/0x2b30 net/core/dev.c:4221
dev_queue_xmit+0x24/0x34 net/core/dev.c:4254
alb_send_lp_vid+0x2a8/0x5c4 drivers/net/bonding/bond_alb.c:937
alb_send_learning_packets+0x168/0x2d8 drivers/net/bonding/bond_alb.c:999
bond_alb_monitor+0x310/0x1318 drivers/net/bonding/bond_alb.c:1527
HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=b57cfa804330c3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=77595558bad304ba6a00
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e0fe92c80000
dashboard link: https://syzkaller.appspot.com/bug?extid=77595558bad304ba6a00
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1513db7ac80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8088989394e3/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2651d6753959/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3fa3f994f9a/Image-d9b4a0c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+775955...@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 0 PID: 5538 Comm: kworker/u4:4 Not tainted 5.15.98-syzkaller #0
turning off the locking correctness validator.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: bond741 bond_alb_monitor
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3734 [inline]
validate_chain kernel/locking/lockdep.c:3755 [inline]
__lock_acquire+0x1b68/0x7620 kernel/locking/lockdep.c:5011
lock_acquire+0x2b8/0x894 kernel/locking/lockdep.c:5622
local_lock_acquire+0x3c/0x98 include/linux/local_lock_internal.h:29
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3734 [inline]
validate_chain kernel/locking/lockdep.c:3755 [inline]
__lock_acquire+0x1b68/0x7620 kernel/locking/lockdep.c:5011
lock_acquire+0x2b8/0x894 kernel/locking/lockdep.c:5622
___slab_alloc+0x1fc/0xdbc mm/slub.c:2930
__slab_alloc mm/slub.c:3095 [inline]
slab_alloc_node mm/slub.c:3186 [inline]
slab_alloc mm/slub.c:3228 [inline]
kmem_cache_alloc+0x340/0x4c4 mm/slub.c:3233
skb_clone+0x180/0x304 net/core/skbuff.c:1523
dev_queue_xmit_nit+0x1fc/0x944 net/core/dev.c:2290
xmit_one net/core/dev.c:3585 [inline]
dev_hard_start_xmit+0x124/0xc10 net/core/dev.c:3606
__dev_queue_xmit+0x1430/0x2b30 net/core/dev.c:4221
dev_queue_xmit+0x24/0x34 net/core/dev.c:4254
alb_send_lp_vid+0x2a8/0x5c4 drivers/net/bonding/bond_alb.c:937
alb_send_learning_packets+0x168/0x2d8 drivers/net/bonding/bond_alb.c:999
bond_alb_monitor+0x310/0x1318 drivers/net/bonding/bond_alb.c:1527
syzbot
Mar 10, 2023, 12:53:36 AM3/10/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d17deac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166a13eac80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f10713d1fd0f/disk-42616e0f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a44ba...@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
CPU: 1 PID: 4587 Comm: kworker/u4:4 Not tainted 6.1.15-syzkaller #0
put_cpu_partial+0x68/0x1fc mm/slub.c:2634
get_partial_node+0x158/0x3fc mm/slub.c:2234
get_partial mm/slub.c:2325 [inline]
___slab_alloc+0x6b8/0xf08 mm/slub.c:3175
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc+0x2cc/0x37c mm/slub.c:3422
skb_clone+0x19c/0x304 net/core/skbuff.c:1650
dev_queue_xmit_nit+0x1fc/0x990 net/core/dev.c:2265
xmit_one net/core/dev.c:3586 [inline]
dev_hard_start_xmit+0x138/0xc94 net/core/dev.c:3606
sch_direct_xmit+0x234/0x548 net/sched/sch_generic.c:342
__dev_xmit_skb net/core/dev.c:3817 [inline]
__dev_queue_xmit+0x14f4/0x3488 net/core/dev.c:4222
dev_queue_xmit_accel include/linux/netdevice.h:3021 [inline]
macvlan_queue_xmit drivers/net/macvlan.c:547 [inline]
macvlan_start_xmit+0x304/0x674 drivers/net/macvlan.c:571
__netdev_start_xmit include/linux/netdevice.h:4847 [inline]
netdev_start_xmit include/linux/netdevice.h:4861 [inline]
xmit_one net/core/dev.c:3590 [inline]
dev_hard_start_xmit+0x324/0xc94 net/core/dev.c:3606
__dev_queue_xmit+0x16d8/0x3488 net/core/dev.c:4256
dev_queue_xmit include/linux/netdevice.h:3015 [inline]
alb_send_lp_vid+0x2ac/0x5c8 drivers/net/bonding/bond_alb.c:949
alb_send_learning_packets+0x168/0x2d8 drivers/net/bonding/bond_alb.c:1011
bond_alb_monitor+0x310/0x12fc drivers/net/bonding/bond_alb.c:1563
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=650737f7e9682672
dashboard link: https://syzkaller.appspot.com/bug?extid=7a44bac76a5b55f56fcd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1789b888c80000
dashboard link: https://syzkaller.appspot.com/bug?extid=7a44bac76a5b55f56fcd
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=166a13eac80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f10713d1fd0f/disk-42616e0f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5a1307bb774e/vmlinux-42616e0f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388238a30fe4/Image-42616e0f.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a44ba...@syzkaller.appspotmail.com
BUG: MAX_LOCKDEP_CHAINS too low!
turning off the locking correctness validator.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: bond259 bond_alb_monitor
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/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3778 [inline]
validate_chain kernel/locking/lockdep.c:3799 [inline]
__lock_acquire+0x1b8c/0x764c kernel/locking/lockdep.c:5055
lock_acquire+0x2f8/0x8dc kernel/locking/lockdep.c:5668
local_lock_acquire+0x3c/0x98 include/linux/local_lock_internal.h:29
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/0x58 lib/dump_stack.c:113
lookup_chain_cache_add kernel/locking/lockdep.c:3778 [inline]
validate_chain kernel/locking/lockdep.c:3799 [inline]
__lock_acquire+0x1b8c/0x764c kernel/locking/lockdep.c:5055
lock_acquire+0x2f8/0x8dc kernel/locking/lockdep.c:5668
put_cpu_partial+0x68/0x1fc mm/slub.c:2634
get_partial_node+0x158/0x3fc mm/slub.c:2234
get_partial mm/slub.c:2325 [inline]
___slab_alloc+0x6b8/0xf08 mm/slub.c:3175
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc+0x2cc/0x37c mm/slub.c:3422
skb_clone+0x19c/0x304 net/core/skbuff.c:1650
dev_queue_xmit_nit+0x1fc/0x990 net/core/dev.c:2265
xmit_one net/core/dev.c:3586 [inline]
dev_hard_start_xmit+0x138/0xc94 net/core/dev.c:3606
sch_direct_xmit+0x234/0x548 net/sched/sch_generic.c:342
__dev_xmit_skb net/core/dev.c:3817 [inline]
__dev_queue_xmit+0x14f4/0x3488 net/core/dev.c:4222
dev_queue_xmit_accel include/linux/netdevice.h:3021 [inline]
macvlan_queue_xmit drivers/net/macvlan.c:547 [inline]
macvlan_start_xmit+0x304/0x674 drivers/net/macvlan.c:571
__netdev_start_xmit include/linux/netdevice.h:4847 [inline]
netdev_start_xmit include/linux/netdevice.h:4861 [inline]
xmit_one net/core/dev.c:3590 [inline]
dev_hard_start_xmit+0x324/0xc94 net/core/dev.c:3606
__dev_queue_xmit+0x16d8/0x3488 net/core/dev.c:4256
dev_queue_xmit include/linux/netdevice.h:3015 [inline]
alb_send_lp_vid+0x2ac/0x5c8 drivers/net/bonding/bond_alb.c:949
alb_send_learning_packets+0x168/0x2d8 drivers/net/bonding/bond_alb.c:1011
bond_alb_monitor+0x310/0x12fc drivers/net/bonding/bond_alb.c:1563
Reply all
Reply to author
Forward
0 new messages