[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171211191041.GD62691@gmail.com>
Date: Mon, 11 Dec 2017 11:10:41 -0800
From: Eric Biggers <ebiggers3@...il.com>
To: syzbot
<bot+3401d9494b9380f7244bcc7fec49680878fccba6@...kaller.appspotmail.com>
Cc: davem@...emloft.net, herbert@...dor.apana.org.au,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: general protection fault in blkcipher_walk_done
On Mon, Nov 27, 2017 at 10:56:47AM -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
> 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: af_alg - wait for data at beginning of recvmsg
Powered by blists - more mailing lists