From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+afbe81311aa0da046f1e62a665eccddac254f803@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: wild-memory-access Write in scatterwalk_copychunks
Date: Fri, 22 Dec 2017 11:24:58 -0600 [thread overview]
Message-ID: <20171222172458.GC588@zzz.localdomain> (raw)
In-Reply-To: <94eb2c05a380bd8f2a055ffc6de5@google.com>
On Sun, Dec 10, 2017 at 05:31:01AM -0800, syzbot wrote:
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, reply to this email with:
> #syz fix: exact-commit-title
> If you want to test a patch for this bug, please reply with:
> #syz test: git://repo/address.git branch
> and provide the patch inline or as an attachment.
> 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 fix: crypto: chacha20poly1305 - validate the digest size
prev parent reply other threads:[~2017-12-22 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 13:31 KASAN: wild-memory-access Write in scatterwalk_copychunks syzbot
2017-12-11 20:15 ` [PATCH] crypto: chacha20poly1305 - validate the digest size Eric Biggers
2017-12-22 8:34 ` Herbert Xu
2017-12-22 17:24 ` 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=20171222172458.GC588@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+afbe81311aa0da046f1e62a665eccddac254f803@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).