general protection fault in l2tp_xmit_skb
5 views
Skip to first unread message
syzbot
Nov 23, 2019, 1:05:11 PM11/23/19
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: c74386d5 afs: Fix missing timeout reset
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1661f7f6e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4737c15fc47048f2
dashboard link: https://syzkaller.appspot.com/bug?extid=194ba5493c65146a20dc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [da...@davemloft.net edum...@google.com f...@strlen.de
gna...@redhat.com jian....@oracle.com linux-...@vger.kernel.org
net...@vger.kernel.org tg...@linutronix.de yueha...@huawei.com]
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+194ba5...@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11255 Comm: syz-executor.3 Not tainted 5.4.0-rc8-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3828
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f
85 0b 28 00 00 49 81 3e e0 a5 06 8a 0f 84 5f ee ff
RSP: 0018:ffff88805d827760 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000014 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff88805d827878 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff138cf18 R11: ffff8880a3e16700 R12: 00000000000000a0
R13: 0000000000000000 R14: 00000000000000a0 R15: 0000000000000000
FS: 00007fb88bcb7700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2cf31000 CR3: 000000008fcf6000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4487
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2f/0x40 kernel/locking/spinlock.c:151
spin_lock include/linux/spinlock.h:338 [inline]
l2tp_xmit_skb+0x367/0x1200 net/l2tp/l2tp_core.c:1083
pppol2tp_sendmsg+0x4af/0x6c0 net/l2tp/l2tp_ppp.c:325
sock_sendmsg_nosec net/socket.c:637 [inline]
sock_sendmsg+0xd7/0x130 net/socket.c:657
___sys_sendmsg+0x3e2/0x920 net/socket.c:2311
__sys_sendmmsg+0x1bf/0x4d0 net/socket.c:2413
__do_sys_sendmmsg net/socket.c:2442 [inline]
__se_sys_sendmmsg net/socket.c:2439 [inline]
__x64_sys_sendmmsg+0x9d/0x100 net/socket.c:2439
do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a639
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fb88bcb6c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000000000045a639
RDX: 0800000000000059 RSI: 0000000020005fc0 RDI: 000000000000000a
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb88bcb76d4
R13: 00000000004c83c8 R14: 00000000004de808 R15: 00000000ffffffff
Modules linked in:
---[ end trace df79b13eeedd2573 ]---
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3828
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f
85 0b 28 00 00 49 81 3e e0 a5 06 8a 0f 84 5f ee ff
RSP: 0018:ffff88805d827760 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000014 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff88805d827878 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff138cf18 R11: ffff8880a3e16700 R12: 00000000000000a0
R13: 0000000000000000 R14: 00000000000000a0 R15: 0000000000000000
FS: 00007fb88bcb7700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2cf31000 CR3: 000000008fcf6000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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 found the following crash on:
HEAD commit: c74386d5 afs: Fix missing timeout reset
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1661f7f6e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4737c15fc47048f2
dashboard link: https://syzkaller.appspot.com/bug?extid=194ba5493c65146a20dc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [da...@davemloft.net edum...@google.com f...@strlen.de
gna...@redhat.com jian....@oracle.com linux-...@vger.kernel.org
net...@vger.kernel.org tg...@linutronix.de yueha...@huawei.com]
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+194ba5...@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 11255 Comm: syz-executor.3 Not tainted 5.4.0-rc8-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3828
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f
85 0b 28 00 00 49 81 3e e0 a5 06 8a 0f 84 5f ee ff
RSP: 0018:ffff88805d827760 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000014 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff88805d827878 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff138cf18 R11: ffff8880a3e16700 R12: 00000000000000a0
R13: 0000000000000000 R14: 00000000000000a0 R15: 0000000000000000
FS: 00007fb88bcb7700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2cf31000 CR3: 000000008fcf6000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
lock_acquire+0x190/0x410 kernel/locking/lockdep.c:4487
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2f/0x40 kernel/locking/spinlock.c:151
spin_lock include/linux/spinlock.h:338 [inline]
l2tp_xmit_skb+0x367/0x1200 net/l2tp/l2tp_core.c:1083
pppol2tp_sendmsg+0x4af/0x6c0 net/l2tp/l2tp_ppp.c:325
sock_sendmsg_nosec net/socket.c:637 [inline]
sock_sendmsg+0xd7/0x130 net/socket.c:657
___sys_sendmsg+0x3e2/0x920 net/socket.c:2311
__sys_sendmmsg+0x1bf/0x4d0 net/socket.c:2413
__do_sys_sendmmsg net/socket.c:2442 [inline]
__se_sys_sendmmsg net/socket.c:2439 [inline]
__x64_sys_sendmmsg+0x9d/0x100 net/socket.c:2439
do_syscall_64+0xfa/0x760 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45a639
Code: ad b6 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 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fb88bcb6c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000000000045a639
RDX: 0800000000000059 RSI: 0000000020005fc0 RDI: 000000000000000a
RBP: 000000000075bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb88bcb76d4
R13: 00000000004c83c8 R14: 00000000004de808 R15: 00000000ffffffff
Modules linked in:
---[ end trace df79b13eeedd2573 ]---
RIP: 0010:__lock_acquire+0x1254/0x4a00 kernel/locking/lockdep.c:3828
Code: 00 0f 85 96 24 00 00 48 81 c4 f0 00 00 00 5b 41 5c 41 5d 41 5e 41 5f
5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <80> 3c 02 00 0f
85 0b 28 00 00 49 81 3e e0 a5 06 8a 0f 84 5f ee ff
RSP: 0018:ffff88805d827760 EFLAGS: 00010006
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000014 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff88805d827878 R08: 0000000000000001 R09: 0000000000000001
R10: fffffbfff138cf18 R11: ffff8880a3e16700 R12: 00000000000000a0
R13: 0000000000000000 R14: 00000000000000a0 R15: 0000000000000000
FS: 00007fb88bcb7700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2cf31000 CR3: 000000008fcf6000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
---
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
Feb 18, 2020, 4:56:08 PM2/18/20
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages