From: syzbot <syzbot+88f4b1e6cf88da11f5cd@syzkaller•appspotmail.com>
To: davem@davemloft•net, dhowells@redhat•com,
herbert@gondor•apana.org.au, linux-crypto@vger•kernel.org,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
pabeni@redhat•com, syzkaller-bugs@googlegroups•com
Subject: Re: [syzbot] [crypto?] general protection fault in shash_ahash_update
Date: Mon, 19 Jun 2023 11:39:28 -0700 [thread overview]
Message-ID: <000000000000c6527105fe7fdab8@google.com> (raw)
In-Reply-To: <000000000000ada87505fe7cf809@google.com>
syzbot has bisected this issue to:
commit c662b043cdca89bf0f03fc37251000ac69a3a548
Author: David Howells <dhowells@redhat•com>
Date: Tue Jun 6 13:08:56 2023 +0000
crypto: af_alg/hash: Support MSG_SPLICE_PAGES
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a7cbcf280000
start commit: 9a94d764e9bc Merge tag 'mlx5-updates-2023-06-16' of git://..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16a7cbcf280000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a7cbcf280000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4a7d74e6a7c3211
dashboard link: https://syzkaller.appspot.com/bug?extid=88f4b1e6cf88da11f5cd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1152c4ff280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1307cbcf280000
Reported-by: syzbot+88f4b1e6cf88da11f5cd@syzkaller•appspotmail.com
Fixes: c662b043cdca ("crypto: af_alg/hash: Support MSG_SPLICE_PAGES")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-19 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:13 [syzbot] [crypto?] general protection fault in shash_ahash_update syzbot
2023-06-19 18:39 ` syzbot [this message]
2023-06-19 21:45 ` David Howells
2023-06-19 22:09 ` syzbot
2023-06-20 7:43 ` David Howells
2023-06-20 8:09 ` syzbot
2023-07-25 15:18 ` David Howells
2023-07-19 17:42 ` syzbot
2023-07-19 17:56 ` Aleksandr Nogikh
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=000000000000c6527105fe7fdab8@google.com \
--to=syzbot+88f4b1e6cf88da11f5cd@syzkaller$(echo .)appspotmail.com \
--cc=davem@davemloft$(echo .)net \
--cc=dhowells@redhat$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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