From: syzbot <syzbot+cdc562bc26a2b2b0a94f@syzkaller.appspotmail.com>
To: airlied@linux.ie, dmitry.kasatkin@gmail.com,
dri-devel@lists.freedesktop.org, james.l.morris@oracle.com,
jmorris@namei.org, jsarha@ti.com,
linux-ima-devel@lists.sourceforge.net,
linux-ima-user@lists.sourceforge.net,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, tomi.valkeinen@ti.com,
zohar@linux.vnet.ibm.com
Subject: Re: INFO: task hung in process_measurement
Date: Fri, 22 Mar 2019 23:58:00 -0700 [thread overview]
Message-ID: <000000000000f8654a0584bd7d5d@google.com> (raw)
In-Reply-To: <00000000000033ebee0577262a98@google.com>
syzbot has bisected this bug to:
commit 8fe5616b20e5742bb5fee0e77dffe2fc76ac92a0
Author: Jyri Sarha <jsarha@ti.com>
Date: Tue Jun 14 08:43:30 2016 +0000
drm/tilcdc: Restore old dpms state in pm_resume()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10daff1b200000
start commit: 291d0e5d Merge tag 'for-linus-20180929' of git://git.kerne..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=12daff1b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=14daff1b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=a8212f992609a887
dashboard link: https://syzkaller.appspot.com/bug?extid=cdc562bc26a2b2b0a94f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=140e285e400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1237fe81400000
Reported-by: syzbot+cdc562bc26a2b2b0a94f@syzkaller.appspotmail.com
Fixes: 8fe5616b20e5 ("drm/tilcdc: Restore old dpms state in pm_resume()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-23 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 7:58 INFO: task hung in process_measurement syzbot
2019-03-23 6:58 ` syzbot [this message]
2019-03-25 11:57 ` Tomi Valkeinen
2019-03-25 11:57 ` Tomi Valkeinen
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=000000000000f8654a0584bd7d5d@google.com \
--to=syzbot+cdc562bc26a2b2b0a94f@syzkaller.appspotmail.com \
--cc=airlied@linux.ie \
--cc=dmitry.kasatkin@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.l.morris@oracle.com \
--cc=jmorris@namei.org \
--cc=jsarha@ti.com \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-ima-user@lists.sourceforge.net \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tomi.valkeinen@ti.com \
--cc=zohar@linux.vnet.ibm.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 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.