public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0871b14ca2e2fb64f6e3@syzkaller.appspotmail.com>
To: airlied@linux.ie, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, hamohammed.sa@gmail.com,
	linux-kernel@vger.kernel.org, rodrigosiqueiramelo@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: WARNING in vkms_vblank_simulate
Date: Mon, 11 Mar 2019 05:28:01 -0700	[thread overview]
Message-ID: <00000000000011f13c0583d0b48c@google.com> (raw)

syzbot has bisected this bug to:

commit 09ef09b4ab95dc405ad4171ec2cd8a4ff5227108
Author: Shayenne Moura <shayenneluzmoura@gmail.com>
Date:   Wed Feb 6 20:08:13 2019 +0000

     drm/vkms: WARN when hrtimer_forward_now fails

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=128448cf200000
start commit:   09ef09b4 drm/vkms: WARN when hrtimer_forward_now fails
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=118448cf200000
console output: https://syzkaller.appspot.com/x/log.txt?x=168448cf200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c1e0e0ec44d1e5ff
dashboard link: https://syzkaller.appspot.com/bug?extid=0871b14ca2e2fb64f6e3
userspace arch: amd64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1787db8d200000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17fc9883200000

Reported-by: syzbot+0871b14ca2e2fb64f6e3@syzkaller.appspotmail.com
Fixes: 09ef09b4 ("drm/vkms: WARN when hrtimer_forward_now fails")

             reply	other threads:[~2019-03-11 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 12:28 syzbot [this message]
2019-03-11 13:06 ` WARNING in vkms_vblank_simulate Dmitry Vyukov
  -- strict thread matches above, loose matches on Subject: below --
2019-03-11 12:05 syzbot
2019-02-11 22:03 syzbot

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=00000000000011f13c0583d0b48c@google.com \
    --to=syzbot+0871b14ca2e2fb64f6e3@syzkaller.appspotmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hamohammed.sa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigosiqueiramelo@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox