From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+86a008206e8012f85c5feebf2873716e50f33fc4@syzkaller.appspotmail.com>
Cc: adobriyan@gmail.com, akinobu.mita@gmail.com,
akpm@linux-foundation.org, dvyukov@google.com,
ebiederm@xmission.com, jani.nikula@intel.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
syzkaller-bugs@googlegroups.com, vegard.nossum@oracle.com
Subject: Re: possible deadlock in lock_trace
Date: Tue, 12 Dec 2017 13:28:38 -0800 [thread overview]
Message-ID: <20171212212838.GG185376@gmail.com> (raw)
In-Reply-To: <f40304381824e411e9055f37909c@google.com>
On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote:
>
> 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.
> Note: all commands must start from beginning of the line in the email body.
>
#syz dup: possible deadlock in seq_read
next prev parent reply other threads:[~2017-12-12 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f40304381824e411e9055f37909c@google.com>
2017-12-03 22:25 ` possible deadlock in lock_trace syzbot
2017-12-12 21:28 ` Eric Biggers [this message]
2017-12-12 21:59 ` Eric Biggers
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=20171212212838.GG185376@gmail.com \
--to=ebiggers3@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bot+86a008206e8012f85c5feebf2873716e50f33fc4@syzkaller.appspotmail.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vegard.nossum@oracle.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).