general protection fault in __x86_indirect_thunk_rbx
93 views
Skip to first unread message
syzbot
Nov 7, 2018, 12:03:05 AM11/7/18
to bfi...@fieldses.org, jla...@kernel.org, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
Hello,
syzbot found the following crash on:
HEAD commit: d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae9825400000
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
compiler: gcc (GCC) 8.0.1 20180413 (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+83e12c...@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: 1 PID: 9939 Comm: syz-executor5 Not tainted 4.20.0-rc1-next-20181107+
#107
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff88019f166eb0 EFLAGS: 00010293
RAX: ffff8801c298a680 RBX: 5f415e415d415c41 RCX: ffffffff81ed555d
kobject: 'loop2' (000000005961f4a7): kobject_uevent_env
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff88019f166f38
RBP: ffff88019f1670a0 R08: ffff8801c298a680 R09: ffffed003b5e5b67
kobject: 'loop2' (000000005961f4a7): fill_kobj_path: path
= '/devices/virtual/block/loop2'
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801ce6465c0
R13: ffff88019f166f38 R14: 1ffff10033e2cddb R15: dffffc0000000000
FS: 00007fdc2a4eb700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000072c000 CR3: 000000019fde7000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
locks_remove_file+0x148/0x5c0 fs/locks.c:2607
__fput+0x2f0/0xa70 fs/file_table.c:271
____fput+0x15/0x20 fs/file_table.c:312
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1ad1/0x26d0 kernel/exit.c:867
do_group_exit+0x177/0x440 kernel/exit.c:970
get_signal+0x8a8/0x1970 kernel/signal.c:2517
do_signal+0x9c/0x21c0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2e5/0x380 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: fd b3 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 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fdc2a4eac78 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffe0 RBX: 0000000000000006 RCX: 0000000000457569
RDX: 000000000000029f RSI: 0000000020a88f88 RDI: 0000000000000005
RBP: 000000000072bf00 R08: 0000000020e68000 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fdc2a4eb6d4
R13: 00000000004c3b86 R14: 00000000004d5cc8 R15: 00000000ffffffff
Modules linked in:
---[ end trace f409c0e248b1eb30 ]---
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff88019f166eb0 EFLAGS: 00010293
RAX: ffff8801c298a680 RBX: 5f415e415d415c41 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff88019f166f38
RBP: ffff88019f1670a0 R08: ffff8801c298a680 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801ce6465c0
audit: type=1326 audit(1541560871.105:63): auid=4294967295 uid=0 gid=0
ses=4294967295 subj==unconfined pid=9895 comm="syz-executor3"
exe="/root/syz-executor3" sig=9 arch=c000003e syscall=228 compat=0
ip=0x45a3ca code=0x0
R13: ffff88019f166f38 R14: 1ffff10033e2cddb R15: dffffc0000000000
FS: 00007fdc2a4eb700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
kobject: 'loop4' (00000000e724a344): kobject_uevent_env
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kobject: 'loop4' (00000000e724a344): fill_kobj_path: path
= '/devices/virtual/block/loop4'
kobject: 'kvm' (00000000c2eca0f7): kobject_uevent_env
kobject: 'loop3' (00000000e5653105): kobject_uevent_env
kobject: 'kvm' (00000000c2eca0f7): fill_kobj_path: path
= '/devices/virtual/misc/kvm'
kobject: 'loop3' (00000000e5653105): fill_kobj_path: path
= '/devices/virtual/block/loop3'
CR2: 00007fe26d074db8 CR3: 00000001a2d54000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kobject: 'kvm' (00000000c2eca0f7): kobject_uevent_env
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
kobject: 'kvm' (00000000c2eca0f7): fill_kobj_path: path
= '/devices/virtual/misc/kvm'
kobject: 'loop0' (00000000b5ef668f): kobject_uevent_env
---
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#bug-status-tracking for how to communicate with
syzbot.
syzbot found the following crash on:
HEAD commit: d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10ae9825400000
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
compiler: gcc (GCC) 8.0.1 20180413 (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+83e12c...@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: 1 PID: 9939 Comm: syz-executor5 Not tainted 4.20.0-rc1-next-20181107+
#107
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff88019f166eb0 EFLAGS: 00010293
RAX: ffff8801c298a680 RBX: 5f415e415d415c41 RCX: ffffffff81ed555d
kobject: 'loop2' (000000005961f4a7): kobject_uevent_env
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff88019f166f38
RBP: ffff88019f1670a0 R08: ffff8801c298a680 R09: ffffed003b5e5b67
kobject: 'loop2' (000000005961f4a7): fill_kobj_path: path
= '/devices/virtual/block/loop2'
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801ce6465c0
R13: ffff88019f166f38 R14: 1ffff10033e2cddb R15: dffffc0000000000
FS: 00007fdc2a4eb700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000072c000 CR3: 000000019fde7000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
locks_remove_file+0x148/0x5c0 fs/locks.c:2607
__fput+0x2f0/0xa70 fs/file_table.c:271
____fput+0x15/0x20 fs/file_table.c:312
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1ad1/0x26d0 kernel/exit.c:867
do_group_exit+0x177/0x440 kernel/exit.c:970
get_signal+0x8a8/0x1970 kernel/signal.c:2517
do_signal+0x9c/0x21c0 arch/x86/kernel/signal.c:816
exit_to_usermode_loop+0x2e5/0x380 arch/x86/entry/common.c:162
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath arch/x86/entry/common.c:268 [inline]
do_syscall_64+0x6be/0x820 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: fd b3 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 cb b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fdc2a4eac78 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffe0 RBX: 0000000000000006 RCX: 0000000000457569
RDX: 000000000000029f RSI: 0000000020a88f88 RDI: 0000000000000005
RBP: 000000000072bf00 R08: 0000000020e68000 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fdc2a4eb6d4
R13: 00000000004c3b86 R14: 00000000004d5cc8 R15: 00000000ffffffff
Modules linked in:
---[ end trace f409c0e248b1eb30 ]---
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff88019f166eb0 EFLAGS: 00010293
RAX: ffff8801c298a680 RBX: 5f415e415d415c41 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff88019f166f38
RBP: ffff88019f1670a0 R08: ffff8801c298a680 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801ce6465c0
audit: type=1326 audit(1541560871.105:63): auid=4294967295 uid=0 gid=0
ses=4294967295 subj==unconfined pid=9895 comm="syz-executor3"
exe="/root/syz-executor3" sig=9 arch=c000003e syscall=228 compat=0
ip=0x45a3ca code=0x0
R13: ffff88019f166f38 R14: 1ffff10033e2cddb R15: dffffc0000000000
FS: 00007fdc2a4eb700(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
kobject: 'loop4' (00000000e724a344): kobject_uevent_env
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kobject: 'loop4' (00000000e724a344): fill_kobj_path: path
= '/devices/virtual/block/loop4'
kobject: 'kvm' (00000000c2eca0f7): kobject_uevent_env
kobject: 'loop3' (00000000e5653105): kobject_uevent_env
kobject: 'kvm' (00000000c2eca0f7): fill_kobj_path: path
= '/devices/virtual/misc/kvm'
kobject: 'loop3' (00000000e5653105): fill_kobj_path: path
= '/devices/virtual/block/loop3'
CR2: 00007fe26d074db8 CR3: 00000001a2d54000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kobject: 'kvm' (00000000c2eca0f7): kobject_uevent_env
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
kobject: 'kvm' (00000000c2eca0f7): fill_kobj_path: path
= '/devices/virtual/misc/kvm'
kobject: 'loop0' (00000000b5ef668f): kobject_uevent_env
---
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#bug-status-tracking for how to communicate with
syzbot.
syzbot
Nov 7, 2018, 2:47:04 AM11/7/18
to bfi...@fieldses.org, jla...@kernel.org, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
syzbot has found a reproducer for the following crash on:
HEAD commit: d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=169e9825400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+83e12c...@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: 1 PID: 5670 Comm: syz-executor439 Not tainted
RAX: ffff8801d49723c0 RBX: 894cdffffc000000 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff8801d89af338
RBP: ffff8801d89af4a0 R08: ffff8801d49723c0 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801d798da00
R13: ffff8801d89af338 R14: 1ffff1003b135e5b R15: dffffc0000000000
FS: 0000000001292880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
__se_sys_exit_group kernel/exit.c:979 [inline]
__x64_sys_exit_group+0x3e/0x50 kernel/exit.c:979
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ec48
Code: Bad RIP value.
RSP: 002b:00007fff104a8308 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ec48
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004be508 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d0180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace db9bef1a2174e463 ]---
RAX: ffff8801d49723c0 RBX: 894cdffffc000000 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff8801d89af338
RBP: ffff8801d89af4a0 R08: ffff8801d49723c0 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801d798da00
R13: ffff8801d89af338 R14: 1ffff1003b135e5b R15: dffffc0000000000
FS: 0000000001292880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
HEAD commit: d881de30d29e Add linux-next specific files for 20181107
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+83e12c...@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
4.20.0-rc1-next-20181107+ #107
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff8801d89af2b0 EFLAGS: 00010293
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RAX: ffff8801d49723c0 RBX: 894cdffffc000000 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff8801d89af338
RBP: ffff8801d89af4a0 R08: ffff8801d49723c0 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801d798da00
R13: ffff8801d89af338 R14: 1ffff1003b135e5b R15: dffffc0000000000
FS: 0000000001292880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020e2aff8 CR3: 000000000946a000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
locks_remove_file+0x148/0x5c0 fs/locks.c:2607
__fput+0x2f0/0xa70 fs/file_table.c:271
____fput+0x15/0x20 fs/file_table.c:312
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1ad1/0x26d0 kernel/exit.c:867
do_group_exit+0x177/0x440 kernel/exit.c:970
__do_sys_exit_group kernel/exit.c:981 [inline]
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
locks_remove_file+0x148/0x5c0 fs/locks.c:2607
__fput+0x2f0/0xa70 fs/file_table.c:271
____fput+0x15/0x20 fs/file_table.c:312
task_work_run+0x1e8/0x2a0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0x1ad1/0x26d0 kernel/exit.c:867
do_group_exit+0x177/0x440 kernel/exit.c:970
__se_sys_exit_group kernel/exit.c:979 [inline]
__x64_sys_exit_group+0x3e/0x50 kernel/exit.c:979
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x43ec48
Code: Bad RIP value.
RSP: 002b:00007fff104a8308 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000043ec48
RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
RBP: 00000000004be508 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d0180 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace db9bef1a2174e463 ]---
RIP: 0010:__x86_indirect_thunk_rbx+0x10/0x20 arch/x86/lib/retpoline.S:33
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RSP: 0018:ffff8801d89af2b0 EFLAGS: 00010293
Code: 90 0f ae e8 eb f9 48 89 04 24 c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00
00 00 00 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 1c 24 <c3> 0f 1f 44 00
00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3
RAX: ffff8801d49723c0 RBX: 894cdffffc000000 RCX: ffffffff81ed555d
RDX: 0000000000000000 RSI: ffffffff81ed5c9e RDI: ffff8801d89af338
RBP: ffff8801d89af4a0 R08: ffff8801d49723c0 R09: ffffed003b5e5b67
R10: ffffed003b5e5b67 R11: ffff8801daf2db3b R12: ffff8801d798da00
R13: ffff8801d89af338 R14: 1ffff1003b135e5b R15: dffffc0000000000
FS: 0000000001292880(0000) GS:ffff8801daf00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000043ec1e CR3: 000000000946a000 CR4: 00000000001406e0
syzbot
Mar 21, 2019, 1:32:00 AM3/21/19
to bfi...@fieldses.org, jla...@kernel.org, linux-...@vger.kernel.org, linux-...@vger.kernel.org, ne...@suse.com, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
syzbot has bisected this bug to:
commit dee160df820de41ff2f59a715643680822a0ab06
Author: NeilBrown <ne...@suse.com>
Date: Mon Nov 5 01:30:47 2018 +0000
locks: use properly initialized file_lock when unlocking.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000
start commit: dee160df locks: use properly initialized file_lock when un..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000
Fixes: dee160df ("locks: use properly initialized file_lock when
unlocking.")
commit dee160df820de41ff2f59a715643680822a0ab06
Author: NeilBrown <ne...@suse.com>
Date: Mon Nov 5 01:30:47 2018 +0000
locks: use properly initialized file_lock when unlocking.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000
start commit: dee160df locks: use properly initialized file_lock when un..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
Reported-by: syzbot+83e12c...@syzkaller.appspotmail.com
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
Fixes: dee160df ("locks: use properly initialized file_lock when
unlocking.")
NeilBrown
Mar 21, 2019, 2:08:10 AM3/21/19
to syzbot, bfi...@fieldses.org, jla...@kernel.org, linux-...@vger.kernel.org, linux-...@vger.kernel.org, syzkall...@googlegroups.com, vi...@zeniv.linux.org.uk
On Wed, Mar 20 2019, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit dee160df820de41ff2f59a715643680822a0ab06
> Author: NeilBrown <ne...@suse.com>
> Date: Mon Nov 5 01:30:47 2018 +0000
>
> locks: use properly initialized file_lock when unlocking.
This commit did not make it to mainline.
> syzbot has bisected this bug to:
>
> commit dee160df820de41ff2f59a715643680822a0ab06
> Author: NeilBrown <ne...@suse.com>
> Date: Mon Nov 5 01:30:47 2018 +0000
>
> locks: use properly initialized file_lock when unlocking.
It was replaced by
Commit d6367d624137 ("fs/locks: use properly initialized file_lock when unlocking.")
which added a call to locks_init_lock() in flock_make_lock().
NeilBrown
Dmitry Vyukov
Mar 21, 2019, 2:16:47 AM3/21/19
to NeilBrown, syzbot, Bruce Fields, Jeff Layton, linux-fsdevel, LKML, syzkaller-bugs, Al Viro
On Thu, Mar 21, 2019 at 7:08 AM NeilBrown <ne...@suse.com> wrote:
>
> On Wed, Mar 20 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit dee160df820de41ff2f59a715643680822a0ab06
> > Author: NeilBrown <ne...@suse.com>
> > Date: Mon Nov 5 01:30:47 2018 +0000
> >
> > locks: use properly initialized file_lock when unlocking.
>
> This commit did not make it to mainline.
> It was replaced by
>
> Commit d6367d624137 ("fs/locks: use properly initialized file_lock when unlocking.")
>
> which added a call to locks_init_lock() in flock_make_lock().
>
> NeilBrown
Hi Neil,
>
> On Wed, Mar 20 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit dee160df820de41ff2f59a715643680822a0ab06
> > Author: NeilBrown <ne...@suse.com>
> > Date: Mon Nov 5 01:30:47 2018 +0000
> >
> > locks: use properly initialized file_lock when unlocking.
>
> This commit did not make it to mainline.
> It was replaced by
>
> Commit d6367d624137 ("fs/locks: use properly initialized file_lock when unlocking.")
>
> which added a call to locks_init_lock() in flock_make_lock().
>
> NeilBrown
You are talking to robot. Robot does not understand English prose ;)
Here is info on how to talk to it:
In this case I think we need to say:
#syz fix: fs/locks: use properly initialized file_lock when unlocking.
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000
> > start commit: dee160df locks: use properly initialized file_lock when un..
> > git tree: linux-next
> > final crash: https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
> > dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
> >
> > Reported-by: syzbot+83e12c...@syzkaller.appspotmail.com
> > Fixes: dee160df ("locks: use properly initialized file_lock when
> > unlocking.")
>
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bug...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/87lg187oao.fsf%40notabene.neil.brown.name.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages