general protection fault in smc_setsockopt
14 views
Skip to first unread message
syzbot
Mar 1, 2018, 3:45:06 AM3/1/18
to da...@davemloft.net, linux-...@vger.kernel.org, linux...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com, ubr...@linux.vnet.ibm.com
Hello,
syzbot hit the following crash on upstream commit
c89be5242607d8aa08a6fa45a887c68b2d4a2a2c (Sun Feb 25 21:43:18 2018 +0000)
Merge tag 'nfs-for-4.16-3' of
git://git.linux-nfs.org/projects/trondmy/linux-nfs
So far this crash happened 21 times on net-next, upstream.
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9045fc...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
net_ratelimit: 10 callbacks suppressed
IPv6: veth1: IPv6 duplicate address fe80::6:10 used by aa:aa:aa:aa:06:10
detected!
xt_connbytes: Forcing CT accounting to be enabled
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
kasan: CONFIG_KASAN_INLINE enabled
Modules linked in:
CPU: 0 PID: 8593 Comm: syz-executor3 Not tainted 4.16.0-rc2+ #329
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288
kasan: GPF could be caused by NULL-ptr deref or user memory access
RSP: 0018:ffff8801d363fcd0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a42516
RDX: 0000000000000005 RSI: ffffc900044fa000 RDI: 0000000000000028
RBP: ffff8801d363fd00 R08: 0000000000000160 R09: 1ffff1003a6c7f1f
R10: 0000000000000003 R11: 0000000000000000 R12: ffff8801d363fdd8
R13: 0000000000000006 R14: 000000000000000e R15: 0000000020000000
FS: 00007fb430913700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006fa0f8 CR3: 00000001b4275004 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
SYSC_setsockopt net/socket.c:1849 [inline]
SyS_setsockopt+0x189/0x360 net/socket.c:1828
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007fb430912c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fb4309136d4 RCX: 0000000000453de9
RDX: 000000000000000e RSI: 0000000000000006 RDI: 0000000000000013
RBP: 000000000072bf58 R08: 0000000000000160 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000057f R14: 00000000006f8488 R15: 0000000000000001
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 00 00 00 48 8b 9b 48 04 00 00 48
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 5d 4c 8b 63 28 48 b8 00 00 00 00 00 fc ff df 49
RIP: smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288 RSP: ffff8801d363fcd0
general protection fault: 0000 [#2] SMP KASAN
---[ end trace 5b5d74758268dff6 ]---
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 8598 Comm: syz-executor3 Tainted: G D 4.16.0-rc2+
#329
Kernel panic - not syncing: Fatal exception
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288
RSP: 0018:ffff8801aae57cd0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a42516
RDX: 0000000000000005 RSI: ffffc9000457b000 RDI: 0000000000000028
RBP: ffff8801aae57d00 R08: 0000000000000004 R09: 1ffff100355caf1f
R10: 0000000000000003 R11: ffffed00355caf59 R12: ffff8801aae57dd8
R13: 0000000000000000 R14: 000000000000003f R15: 0000000020000180
FS: 00007fb4308f2700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe7014ddb0 CR3: 00000001b4275004 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
SYSC_setsockopt net/socket.c:1849 [inline]
SyS_setsockopt+0x189/0x360 net/socket.c:1828
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007fb4308f1c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fb4308f26d4 RCX: 0000000000453de9
RDX: 000000000000003f RSI: 0000000000000000 RDI: 0000000000000013
RBP: 000000000072c010 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000521 R14: 00000000006f7bb8 R15: 0000000000000002
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 00 00 00 48 8b 9b 48 04 00 00 48
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 5d 4c 8b 63 28 48 b8 00 00 00 00 00 fc ff df 49
RIP: smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288 RSP: ffff8801aae57cd0
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
syzbot hit the following crash on upstream commit
c89be5242607d8aa08a6fa45a887c68b2d4a2a2c (Sun Feb 25 21:43:18 2018 +0000)
Merge tag 'nfs-for-4.16-3' of
git://git.linux-nfs.org/projects/trondmy/linux-nfs
So far this crash happened 21 times on net-next, upstream.
Unfortunately, I don't have any reproducer for this crash yet.
Raw console output is attached.
compiler: gcc (GCC) 7.1.1 20170620
.config is attached.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9045fc...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed. See footer for
details.
If you forward the report, please keep this part and the footer.
net_ratelimit: 10 callbacks suppressed
IPv6: veth1: IPv6 duplicate address fe80::6:10 used by aa:aa:aa:aa:06:10
detected!
xt_connbytes: Forcing CT accounting to be enabled
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
kasan: CONFIG_KASAN_INLINE enabled
Modules linked in:
CPU: 0 PID: 8593 Comm: syz-executor3 Not tainted 4.16.0-rc2+ #329
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288
kasan: GPF could be caused by NULL-ptr deref or user memory access
RSP: 0018:ffff8801d363fcd0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a42516
RDX: 0000000000000005 RSI: ffffc900044fa000 RDI: 0000000000000028
RBP: ffff8801d363fd00 R08: 0000000000000160 R09: 1ffff1003a6c7f1f
R10: 0000000000000003 R11: 0000000000000000 R12: ffff8801d363fdd8
R13: 0000000000000006 R14: 000000000000000e R15: 0000000020000000
FS: 00007fb430913700(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006fa0f8 CR3: 00000001b4275004 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
SYSC_setsockopt net/socket.c:1849 [inline]
SyS_setsockopt+0x189/0x360 net/socket.c:1828
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007fb430912c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fb4309136d4 RCX: 0000000000453de9
RDX: 000000000000000e RSI: 0000000000000006 RDI: 0000000000000013
RBP: 000000000072bf58 R08: 0000000000000160 R09: 0000000000000000
R10: 0000000020000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 000000000000057f R14: 00000000006f8488 R15: 0000000000000001
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 00 00 00 48 8b 9b 48 04 00 00 48
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 5d 4c 8b 63 28 48 b8 00 00 00 00 00 fc ff df 49
RIP: smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288 RSP: ffff8801d363fcd0
general protection fault: 0000 [#2] SMP KASAN
---[ end trace 5b5d74758268dff6 ]---
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 8598 Comm: syz-executor3 Tainted: G D 4.16.0-rc2+
#329
Kernel panic - not syncing: Fatal exception
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288
RSP: 0018:ffff8801aae57cd0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff85a42516
RDX: 0000000000000005 RSI: ffffc9000457b000 RDI: 0000000000000028
RBP: ffff8801aae57d00 R08: 0000000000000004 R09: 1ffff100355caf1f
R10: 0000000000000003 R11: ffffed00355caf59 R12: ffff8801aae57dd8
R13: 0000000000000000 R14: 000000000000003f R15: 0000000020000180
FS: 00007fb4308f2700(0000) GS:ffff8801db300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe7014ddb0 CR3: 00000001b4275004 CR4: 00000000001606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
SYSC_setsockopt net/socket.c:1849 [inline]
SyS_setsockopt+0x189/0x360 net/socket.c:1828
do_syscall_64+0x280/0x940 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x453de9
RSP: 002b:00007fb4308f1c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fb4308f26d4 RCX: 0000000000453de9
RDX: 000000000000003f RSI: 0000000000000000 RDI: 0000000000000013
RBP: 000000000072c010 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000521 R14: 00000000006f7bb8 R15: 0000000000000002
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 8e 00 00 00 48 8b 9b 48 04 00 00 48
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 5d 4c 8b 63 28 48 b8 00 00 00 00 00 fc ff df 49
RIP: smc_setsockopt+0x8b/0x110 net/smc/af_smc.c:1288 RSP: ffff8801aae57cd0
Dumping ftrace buffer:
(ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
syzbot will keep track of this bug report.
If you forgot to add the Reported-by tag, once the fix for this bug is
merged
into any tree, please reply to this email with:
#syz fix: exact-commit-title
To mark this as a duplicate of another syzbot report, please reply with:
#syz dup: exact-subject-of-another-report
If it's a one-off invalid bug report, please reply with:
#syz invalid
Note: if the crash happens again, it will cause creation of a new bug
report.
Note: all commands must start from beginning of the line in the email body.
syzbot
Apr 20, 2018, 11:49:02 PM4/20/18
to da...@davemloft.net, linux-...@vger.kernel.org, linux...@vger.kernel.org, net...@vger.kernel.org, syzkall...@googlegroups.com, ubr...@linux.ibm.com, ubr...@linux.vnet.ibm.com
syzbot has found reproducer for the following crash on upstream commit
83beed7b2b26f232d782127792dd0cd4362fdc41 (Fri Apr 20 17:56:32 2018 +0000)
Merge branch 'fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=9045fc589fcd196ef522
So far this crash happened 124 times on net-next, upstream.
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6522155797839872
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5566093930266624
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6661555940753408
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9045fc...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.
CPU: 1 PID: 4520 Comm: syzkaller696326 Not tainted 4.17.0-rc1+ #10
RSP: 0018:ffff8801b433fcc8 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000020000000
RDX: 0000000000000005 RSI: ffffffff873e3bf6 RDI: 0000000000000028
RBP: ffff8801b433fcf8 R08: 0000000000000000 R09: ffffed00359a3780
R10: ffffed00359a3780 R11: ffff8801acd1bc03 R12: ffff8801b433fd40
R13: 0000000000000021 R14: 000000000000000d R15: 0000000020000000
FS: 0000000000b01880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
__do_sys_setsockopt net/socket.c:1914 [inline]
__se_sys_setsockopt net/socket.c:1911 [inline]
__x64_sys_setsockopt+0xbe/0x150 net/socket.c:1911
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43fd19
RSP: 002b:00007ffccc4960f8 EFLAGS: 00000217 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043fd19
RDX: 000000000000000d RSI: 0000000000000021 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000020000000 R11: 0000000000000217 R12: 0000000000401640
R13: 00000000004016d0 R14: 0000000000000000 R15: 0000000000000000
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 93 00 00 00 48 8b 9b 50 04 00 00 48
RIP: smc_setsockopt+0x8b/0x120 net/smc/af_smc.c:1287 RSP: ffff8801b433fcc8
---[ end trace 3858d0cd9ce5e4d4 ]---
83beed7b2b26f232d782127792dd0cd4362fdc41 (Fri Apr 20 17:56:32 2018 +0000)
Merge branch 'fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=9045fc589fcd196ef522
So far this crash happened 124 times on net-next, upstream.
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6522155797839872
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5566093930266624
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6661555940753408
Kernel config:
https://syzkaller.appspot.com/x/.config?id=1808800213120130118
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+9045fc...@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Dumping ftrace buffer:
(ftrace buffer empty)
CPU: 1 PID: 4520 Comm: syzkaller696326 Not tainted 4.17.0-rc1+ #10
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:smc_setsockopt+0x8b/0x120 net/smc/af_smc.c:1287
Google 01/01/2011
RSP: 0018:ffff8801b433fcc8 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000020000000
RDX: 0000000000000005 RSI: ffffffff873e3bf6 RDI: 0000000000000028
RBP: ffff8801b433fcf8 R08: 0000000000000000 R09: ffffed00359a3780
R10: ffffed00359a3780 R11: ffff8801acd1bc03 R12: ffff8801b433fd40
R13: 0000000000000021 R14: 000000000000000d R15: 0000000020000000
FS: 0000000000b01880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000562e1fa410d0 CR3: 00000001acf1e000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__sys_setsockopt+0x1bd/0x390 net/socket.c:1903
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__do_sys_setsockopt net/socket.c:1914 [inline]
__se_sys_setsockopt net/socket.c:1911 [inline]
__x64_sys_setsockopt+0xbe/0x150 net/socket.c:1911
do_syscall_64+0x1b1/0x800 arch/x86/entry/common.c:287
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43fd19
RSP: 002b:00007ffccc4960f8 EFLAGS: 00000217 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043fd19
RDX: 000000000000000d RSI: 0000000000000021 RDI: 0000000000000004
RBP: 00000000006ca018 R08: 0000000000000000 R09: 00000000004002c8
R10: 0000000020000000 R11: 0000000000000217 R12: 0000000000401640
R13: 00000000004016d0 R14: 0000000000000000 R15: 0000000000000000
Code: fa 48 c1 ea 03 80 3c 02 00 0f 85 93 00 00 00 48 8b 9b 50 04 00 00 48
b8 00 00 00 00 00 fc ff df 48 8d 7b 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00
75 62 48 b8 00 00 00 00 00 fc ff df 4c 8b 63 28 49
RIP: smc_setsockopt+0x8b/0x120 net/smc/af_smc.c:1287 RSP: ffff8801b433fcc8
---[ end trace 3858d0cd9ce5e4d4 ]---
Reply all
Reply to author
Forward
0 new messages