From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot
<bot+f841f737eaae84758e88c9d3c5aaf4275c1ce556@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in klist_put
Date: Sun, 5 Nov 2017 11:33:27 +0100 [thread overview]
Message-ID: <20171105103327.GA1487@kroah.com> (raw)
In-Reply-To: <94eb2c049582789e47055d37cb34@google.com>
On Sun, Nov 05, 2017 at 01:05:01AM -0700, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 36ef71cae353f88fd6e095e2aaa3e5953af1685d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
<snip>
Thanks for reporting stuff like this, but really, this format of
reporting bugs is horrible, it does not contain any hints as to what you
were doing, nor how to reproduce it at all.
What am I supposed to do with this? How do I know if this bug is ever
resolved? When did it show up? What workload caused it?
A strace really doesn't help much here, do you have a reproducer?
thanks,
greg k-h
next parent reply other threads:[~2017-11-05 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94eb2c049582789e47055d37cb34@google.com>
2017-11-05 10:33 ` Greg KH [this message]
2017-11-06 12:11 ` general protection fault in klist_put 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=20171105103327.GA1487@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bot+f841f737eaae84758e88c9d3c5aaf4275c1ce556@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.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