WARNING in hsr_dev_xmit

4 views
Skip to first unread message

syzbot

unread,
Feb 20, 2021, 4:19:18 PM2/20/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 29c52025 Linux 4.14.221
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1648f4ccd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=83f668f81cfc5600
dashboard link: https://syzkaller.appspot.com/bug?extid=77c5be59cfec8ab7f891

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

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

__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
net/hsr/hsr_forward.c:366: Malformed frame (port_src hsr0)
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0x10a/0x149 lib/fault-inject.c:149
------------[ cut here ]------------
should_failslab+0xd6/0x130 mm/failslab.c:32
WARNING: CPU: 0 PID: 20093 at net/hsr/hsr_forward.c:365 hsr_forward_skb.cold+0xa7/0xef net/hsr/hsr_forward.c:365
slab_pre_alloc_hook mm/slab.h:421 [inline]
slab_alloc mm/slab.c:3376 [inline]
kmem_cache_alloc+0x40/0x3c0 mm/slab.c:3550
Kernel panic - not syncing: panic_on_warn set ...

radix_tree_node_alloc.constprop.0+0x1b0/0x2f0 lib/radix-tree.c:397
idr_get_free_cmn+0x595/0x8d0 lib/radix-tree.c:2170
idr_get_free include/linux/radix-tree.h:369 [inline]
idr_alloc_cmn+0xe8/0x1e0 lib/idr.c:24
idr_alloc include/linux/idr.h:116 [inline]
idr_alloc_cyclic+0xc2/0x1d0 lib/idr.c:56
__kernfs_new_node+0xaf/0x470 fs/kernfs/dir.c:638
kernfs_new_node fs/kernfs/dir.c:677 [inline]
kernfs_create_dir_ns+0x8c/0x200 fs/kernfs/dir.c:998
kernfs_create_dir include/linux/kernfs.h:502 [inline]
internal_create_group+0xe9/0x710 fs/sysfs/group.c:124
loop_sysfs_init drivers/block/loop.c:821 [inline]
loop_set_fd drivers/block/loop.c:946 [inline]
lo_ioctl+0x1137/0x1cd0 drivers/block/loop.c:1417
__blkdev_driver_ioctl block/ioctl.c:297 [inline]
blkdev_ioctl+0x540/0x1830 block/ioctl.c:594
block_ioctl+0xd9/0x120 fs/block_dev.c:1893
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x465dd7
RSP: 002b:00007efdfecbbf48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000004afae8 RCX: 0000000000465dd7
RDX: 0000000000000004 RSI: 0000000000004c00 RDI: 0000000000000005
RBP: 0000000000000005 R08: 0000000000000000 R09: ffffffffffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000004 R14: 00000000200001b0 R15: 0000000000000002
CPU: 0 PID: 20093 Comm: syz-executor.4 Not tainted 4.14.221-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
FAT-fs (loop2): bogus number of reserved sectors
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
FAT-fs (loop2): This doesn't look like a DOS 1.x volume; DOS 2.x BPB is non-zero
__warn.cold+0x20/0x44 kernel/panic.c:547
FAT-fs (loop2): Can't find a valid FAT filesystem
report_bug+0x208/0x250 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:hsr_forward_skb.cold+0xa7/0xef net/hsr/hsr_forward.c:365
RSP: 0018:ffff888091fff8a0 EFLAGS: 00010282
RAX: 000000000000003a RBX: 0000000000000000 RCX: 0000000000000000
RDX: 000000000000fdef RSI: ffffffff81441800 RDI: ffffed10123fff0a
RBP: ffff8880b4ae7480 R08: 000000000000003a R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880613d0d00
R13: ffff8880a9558080 R14: ffff8880a9558090 R15: ffff8880b4ae7550
hsr_dev_xmit+0x6b/0xa0 net/hsr/hsr_device.c:242
__netdev_start_xmit include/linux/netdevice.h:4039 [inline]
netdev_start_xmit include/linux/netdevice.h:4048 [inline]
packet_direct_xmit+0x410/0x610 net/packet/af_packet.c:269
packet_snd+0x1393/0x21e0 net/packet/af_packet.c:3024
packet_sendmsg+0x1139/0x2ad0 net/packet/af_packet.c:3049
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
SYSC_sendto net/socket.c:1763 [inline]
SyS_sendto+0x1c7/0x2c0 net/socket.c:1731
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x466019
RSP: 002b:00007f1b2a82c188 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 000000000056bf60 RCX: 0000000000466019
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00000000004bd067 R08: 0000000020000100 R09: 0000000000000014
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000056bf60
R13: 00007ffddb227d4f R14: 00007f1b2a82c300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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,
Jun 20, 2021, 5:19:18 PM6/20/21
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages