From: syzbot <syzbot+689ec3afb1ef07b766b2@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, boqun.feng@gmail.com,
dhowells@redhat.com, herbert@gondor.apana.org.au,
kuba@kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
longman@redhat.com, mingo@redhat.com, netdev@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, will@kernel.org
Subject: Re: [syzbot] [ext4?] general protection fault in ext4_finish_bio
Date: Thu, 06 Jul 2023 22:10:21 -0700 [thread overview]
Message-ID: <000000000000554b8205ffdea64e@google.com> (raw)
In-Reply-To: <000000000000a557cb05ff9ed03b@google.com>
syzbot has bisected this issue to:
commit b6d972f6898308fbe7e693bf8d44ebfdb1cd2dc4
Author: David Howells <dhowells@redhat.com>
Date: Fri Jun 16 11:10:32 2023 +0000
crypto: af_alg/hash: Fix recvmsg() after sendmsg(MSG_MORE)
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e4fa88a80000
start commit: ae230642190a Merge branch 'af_unix-followup-fixes-for-so_p..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1414fa88a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1014fa88a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c9bf1936936ca698
dashboard link: https://syzkaller.appspot.com/bug?extid=689ec3afb1ef07b766b2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136b9d48a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10223cb8a80000
Reported-by: syzbot+689ec3afb1ef07b766b2@syzkaller.appspotmail.com
Fixes: b6d972f68983 ("crypto: af_alg/hash: Fix recvmsg() after sendmsg(MSG_MORE)")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-07 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 1:00 [syzbot] [ext4?] general protection fault in ext4_finish_bio syzbot
2023-07-07 5:10 ` syzbot [this message]
2023-07-07 8:06 ` David Howells
2023-07-07 8:20 ` syzbot
2023-07-07 8:13 ` David Howells
2023-07-07 8:55 ` syzbot
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=000000000000554b8205ffdea64e@google.com \
--to=syzbot+689ec3afb1ef07b766b2@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=will@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 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.