panic: text:ADDR len:LINE put:LINE head:ADDR data:ADDR tail:LINEx2e0 end:LINEx2c0 dev:<NULL>

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: f7fedd5c ANDROID: overlayfs: add __get xattr method
git tree: android-4.14
console output: https://syzkaller.appspot.com/x/log.txt?x=11c1cf8ae00000
kernel config: https://syzkaller.appspot.com/x/.config?x=844cb28a0c5c98da
dashboard link: https://syzkaller.appspot.com/bug?extid=b309171acf1130f3d3e3
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

skbuff: skb_over_panic: text:00000000f0a64f65 len:736 put:72
head:00000000bab2e718 data:00000000bab2e718 tail:0x2e0 end:0x2c0 dev:<NULL>
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:104!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
Modules linked in:
CPU: 0 PID: 10965 Comm: syz-executor.2 Not tainted 4.14.152+ #0
task: 000000003095e20b task.stack: 0000000036f49008
RIP: 0010:skb_panic+0x16c/0x16e net/core/skbuff.c:104
RSP: 0018:ffff8881cbec6dc0 EFLAGS: 00010286
RAX: 0000000000000088 RBX: ffff8881d005d140 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffc90003b74000 RDI: ffffed10397d8daa
RBP: ffffffff8a889c20 R08: 0000000000000088 R09: ffffed103b744ce9
R10: ffffed103b744ce8 R11: ffff8881dba26747 R12: ffffffff8a054d7b
R13: 0000000000000048 R14: ffffffff8a889600 R15: 00000000000002c0
FS: 00007f5349958700(0000) GS:ffff8881dba00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000001d1154005 CR4: 00000000001606b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
skb_over_panic net/core/skbuff.c:109 [inline]
skb_put.cold+0x24/0x24 net/core/skbuff.c:1699
dump_esp_combs net/key/af_key.c:3003 [inline]
pfkey_send_acquire+0x163b/0x23b0 net/key/af_key.c:3224
km_query+0xaf/0x1c0 net/xfrm/xfrm_state.c:1968
xfrm_state_find+0x16ef/0x25a0 net/xfrm/xfrm_state.c:1024
xfrm_tmpl_resolve_one+0x1b5/0x7d0 net/xfrm/xfrm_policy.c:1413
xfrm_tmpl_resolve net/xfrm/xfrm_policy.c:1458 [inline]
xfrm_resolve_and_create_bundle+0x20c/0x2020 net/xfrm/xfrm_policy.c:1755
xfrm_lookup_with_ifid+0x20a/0x1770 net/xfrm/xfrm_policy.c:2078
xfrm_lookup net/xfrm/xfrm_policy.c:2202 [inline]
xfrm_lookup_route+0x36/0x1b0 net/xfrm/xfrm_policy.c:2213
ip_route_output_flow+0x89/0xb0 net/ipv4/route.c:2603
udp_sendmsg+0x13a0/0x1bb0 net/ipv4/udp.c:1025
udpv6_sendmsg+0x12ab/0x2500 net/ipv6/udp.c:1193
inet_sendmsg+0x15b/0x520 net/ipv4/af_inet.c:760
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb7/0x100 net/socket.c:656
___sys_sendmsg+0x368/0x890 net/socket.c:2062
__sys_sendmmsg+0x13c/0x360 net/socket.c:2152
SYSC_sendmmsg net/socket.c:2183 [inline]
SyS_sendmmsg+0x2f/0x50 net/socket.c:2178
do_syscall_64+0x19b/0x520 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x45a219
RSP: 002b:00007f5349957c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000000000045a219
RDX: 00000000000005c3 RSI: 0000000020000240 RDI: 0000000000000004
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f53499586d4
R13: 00000000004c7f9d R14: 00000000004de3c8 R15: 00000000ffffffff
Code: 20 ff 4c 8b 4c 24 10 8b 4b 78 41 56 45 89 e8 4c 89 e2 41 57 48 89 ee
48 c7 c7 40 96 88 8a ff 74 24 10 ff 74 24 20 e8 39 b7 ee fe <0f> 0b e8 d7
91 fd fe 4c 8b 64 24 18 e8 fd 54 20 ff 48 c7 c1 e0
RIP: skb_panic+0x16c/0x16e net/core/skbuff.c:104 RSP: ffff8881cbec6dc0
---[ end trace 0910aaefecee077e ]---


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.