From: Chris Wilson <chris@chris-wilson.co.uk>
To: syzbot
<bot+8de19a03d6fdf256eb2b90ec48916b6f47b9b5a3@syzkaller.appspotmail.com>,
airlied@linux.ie, daniel.vetter@intel.com,
dri-devel@lists.freedesktop.org, jani.nikula@linux.intel.com,
linux-kernel@vger.kernel.org, seanpaul@chromium.org,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in drm_modeset_lock_all
Date: Tue, 31 Oct 2017 12:45:47 +0000 [thread overview]
Message-ID: <150945394709.15081.7550043352916368752@mail.alporthouse.com> (raw)
In-Reply-To: <001a114c9224215c93055c82d03e@google.com>
Quoting syzbot (2017-10-27 09:09:50)
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@googlegroups.com.
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new bug
> report.
Can we use
Reported-by: syzbot <bot+8de19a03d6fdf256eb2b90ec48916b6f47b9b5a3@syzkaller.appspotmail.com>
as a unique tag for tracking purposes?
-Chris
next prev parent reply other threads:[~2017-10-31 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a114c9224215c93055c82d03e@google.com>
2017-10-30 14:24 ` WARNING in drm_modeset_lock_all Chris Wilson
2017-10-31 10:22 ` Daniel Vetter
2017-10-31 12:45 ` Chris Wilson [this message]
2017-10-31 13:03 ` Dmitry Vyukov
2018-02-12 16:10 ` 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=150945394709.15081.7550043352916368752@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=bot+8de19a03d6fdf256eb2b90ec48916b6f47b9b5a3@syzkaller.appspotmail.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).