From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+dc3224b9c8f85af3ad550f98c1bc002062185ea6@syzkaller.appspotmail.com>
Cc: adobriyan@gmail.com, akinobu.mita@gmail.com,
akpm@linux-foundation.org, bfields@redhat.com,
davem@davemloft.net, dvyukov@google.com, ebiederm@xmission.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, schwidefsky@de.ibm.com,
syzkaller-bugs@googlegroups.com, vegard.nossum@oracle.com
Subject: Re: KASAN: global-out-of-bounds Read in show_timer
Date: Mon, 11 Dec 2017 15:14:53 -0800 [thread overview]
Message-ID: <20171211231453.GD48753@gmail.com> (raw)
In-Reply-To: <001a1143d52647b3e3055f46d934@google.com>
On Fri, Dec 01, 2017 at 04:53:01AM -0800, syzbot wrote:
> 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.
> Please credit me with: Reported-by: syzbot <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.
> Note: all commands must start from beginning of the line in the email body.
#syz dup: general protection fault in show_timer
prev parent reply other threads:[~2017-12-11 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1143d52647b3e3055f46d934@google.com>
2017-12-02 2:03 ` KASAN: global-out-of-bounds Read in show_timer syzbot
2017-12-11 23:14 ` Eric Biggers [this message]
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=20171211231453.GD48753@gmail.com \
--to=ebiggers3@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@redhat.com \
--cc=bot+dc3224b9c8f85af3ad550f98c1bc002062185ea6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=schwidefsky@de.ibm.com \
--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 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.