From: syzbot <syzbot+675c45cea768b3819803@syzkaller.appspotmail.com>
To: bp@alien8.de, davem@davemloft.net, herbert@gondor.apana.org.au,
hpa@zytor.com, jakub.kicinski@netronome.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org,
simon.horman@netronome.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: general protection fault in gcmaes_crypt_by_sg (2)
Date: Wed, 19 Feb 2020 03:48:03 -0800 [thread overview]
Message-ID: <00000000000064ab40059eec5c3e@google.com> (raw)
In-Reply-To: <000000000000ca89a80598db0ae5@google.com>
syzbot suspects this bug was fixed by commit:
commit db885e66d268884dc72967279b7e84f522556abc
Author: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Fri Jan 10 12:38:32 2020 +0000
net/tls: fix async operation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16871de9e00000
start commit: 07c4b9e9 Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
dashboard link: https://syzkaller.appspot.com/bug?extid=675c45cea768b3819803
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb0056e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1374f5dee00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net/tls: fix async operation
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-02-19 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 6:37 general protection fault in gcmaes_crypt_by_sg (2) syzbot
2019-12-15 1:11 ` syzbot
2020-02-19 11:48 ` syzbot [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=00000000000064ab40059eec5c3e@google.com \
--to=syzbot+675c45cea768b3819803@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jakub.kicinski@netronome.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).