From: syzbot <syzbot+dccce9b26ba09ca49966@syzkaller.appspotmail.com>
To: john.stultz@linaro.org, linux-kernel@vger.kernel.org,
sboyd@kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: linux-next boot error: general protection fault in __x64_sys_settimeofday
Date: Thu, 14 Nov 2019 02:55:07 -0800 [thread overview]
Message-ID: <0000000000007ce85705974c50e5@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 8466d23e Add linux-next specific files for 20191114
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1057aa1ce00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b7e774ae4847760
dashboard link: https://syzkaller.appspot.com/bug?extid=dccce9b26ba09ca49966
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+dccce9b26ba09ca49966@syzkaller.appspotmail.com
[^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 13.646252][ T4004]
udevd[4004]: starting version 175
^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
[....] Synthesizing the initial hotplug events...udevd[4040]:
rename '/dev/v4l/by-path/platform-vivid.0-video-index3.udev-tmp' '/dev/v4l/by-path/platform-vivid.0-video-index3'
failed: No such file or directory
^[[?25l^[[?1c^[7[ 20.856469][ T4350] general protection fault: 0000 [#1]
PREEMPT SMP KASAN
[^[[1G 20.872048][ T4350] Hardware name: Google Google Comput[^[[32m ok
^[[39;49me Engine/Google Compute Engine, BIOS Google 01/01/2011
^[8[ ^[[?25h^[[?0c done.
20.890197][ T4350] Code: 85 50 ff ff ff 85 c0 0f 85 50 01 00 00 e8 b8 cd 10
00 48 8b 85 48 ff ff ff 48 c1 e8 03 48 89 c2 48 b8 00 00 00 00 00 fc ff df
<80> 3c 02 00 0f 85 8a 01 00 00 49 8b 74 24 08 bf 40 42 0f 00 48 89
[....] Waiting f[ 21.522563][ T4350] RIP: 0010:__do_sys_settimeofday
kernel/time/time.c:210 [inline]
[....] Waiting f[ 21.522563][ T4350] RIP: 0010:__se_sys_settimeofday
kernel/time/time.c:199 [inline]
[....] Waiting f[ 21.522563][ T4350] RIP:
0010:__x64_sys_settimeofday+0x170/0x320 kernel/time/time.c:199
or /dev to be fu[ 21.550076][ T4350] RSP: 0018:ffff888093d0fe58 EFLAGS:
00010206
lly populated...[ 21.557498][ T4350] RAX: dffffc0000000000 RBX:
1ffff110127a1fcd RCX: ffffffff8162e915
---
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#status for how to communicate with syzbot.
next reply other threads:[~2019-11-14 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 10:55 syzbot [this message]
2019-11-14 12:35 ` linux-next boot error: general protection fault in __x64_sys_settimeofday Thomas Gleixner
2019-11-14 12:42 ` Dmitry Vyukov
2019-11-14 12:43 ` Dmitry Vyukov
2019-11-14 13:22 ` Arnd Bergmann
2019-11-14 13:28 ` Dmitry Vyukov
2019-11-14 13:37 ` Arnd Bergmann
2019-11-14 13:39 ` Dmitry Vyukov
2019-11-14 13:51 ` Arnd Bergmann
2019-11-14 15:02 ` Thomas Gleixner
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=0000000000007ce85705974c50e5@google.com \
--to=syzbot+dccce9b26ba09ca49966@syzkaller.appspotmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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.