From: syzbot <syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com>
To: bfields@fieldses.org, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: general protection fault in __x86_indirect_thunk_rbx
Date: Tue, 06 Nov 2018 21:03:04 -0800 [thread overview]
Message-ID: <00000000000089d2c9057a0c083a@google.com> (raw)
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+83e12cf81d2c14842146@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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
next reply other threads:[~2018-11-07 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 5:03 syzbot [this message]
2018-11-07 7:47 ` general protection fault in __x86_indirect_thunk_rbx syzbot
2019-03-21 5:32 ` syzbot
2019-03-21 6:07 ` NeilBrown
2019-03-21 6:16 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000089d2c9057a0c083a@google.com \
--to=syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.