Hello,
syzbot found the following issue on:
HEAD commit: c37da90e Linux 4.19.143
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14f2ca31900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=d162ec57805c4e4d
dashboard link:
https://syzkaller.appspot.com/bug?extid=d98704e1f65e44589b68
compiler: gcc (GCC) 10.1.0-syz 20200507
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+d98704...@syzkaller.appspotmail.com
FAT-fs (loop5): Unrecognized mount option "nnonumtail=1" or missing value
Trying to vfree() bad address (000000000c20895f)
overlayfs: missing 'lowerdir'
WARNING: CPU: 1 PID: 9059 at mm/vmalloc.c:1509 __vunmap+0x31a/0x3f0 mm/vmalloc.c:1509
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 9059 Comm: syz-executor.2 Not tainted 4.19.143-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
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
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:__vunmap+0x31a/0x3f0 mm/vmalloc.c:1509
Code: e9 5d fe ff ff e8 26 5e d1 ff 49 81 ef 00 10 00 00 e9 be fd ff ff e8 15 5e d1 ff 4c 89 e6 48 c7 c7 80 18 93 87 e8 31 54 a5 ff <0f> 0b eb 94 e8 fd 5d d1 ff 4c 89 e6 48 c7 c7 e0 18 93 87 e8 19 54
RSP: 0018:ffff88805139f3b8 EFLAGS: 00010282
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000018678 RSI: ffffffff8154d001 RDI: ffffed100a273e69
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: fffffbfff135d0fe R14: 0000607f5168d5a0 R15: ffffe8ffffd8d5a0
vfree+0x65/0x100 mm/vmalloc.c:1598
ipcomp_free_scratches+0xba/0x140 net/xfrm/xfrm_ipcomp.c:216
ipcomp_free_data net/xfrm/xfrm_ipcomp.c:325 [inline]
ipcomp_init_state+0x768/0xa00 net/xfrm/xfrm_ipcomp.c:377
ipcomp6_init_state+0xc2/0x5b0 net/ipv6/ipcomp6.c:165
__xfrm_init_state+0x555/0xd30 net/xfrm/xfrm_state.c:2314
xfrm_state_construct net/xfrm/xfrm_user.c:626 [inline]
xfrm_add_sa+0x1db2/0x33e4 net/xfrm/xfrm_user.c:683
xfrm_user_rcv_msg+0x411/0x6b0 net/xfrm/xfrm_user.c:2681
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
xfrm_netlink_rcv+0x6b/0x90 net/xfrm/xfrm_user.c:2689
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x6bb/0xc40 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:632
___sys_sendmsg+0x7bb/0x8e0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
overlayfs: missing 'lowerdir'
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45d5b9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f13f3ff2c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002cf00 RCX: 000000000045d5b9
RDX: 0000000000000000 RSI: 0000000020000840 RDI: 0000000000000003
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007fff7a879e6f R14: 00007f13f3ff39c0 R15: 000000000118cf4c
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.