From: syzbot <syzbot+0e905eb8228070c457a0@syzkaller.appspotmail.com>
To: alobakin@pm.me, asml.silence@gmail.com, axboe@kernel.dk,
davem@davemloft.net, gnault@redhat.com,
gregkh@linuxfoundation.org, io-uring@vger.kernel.org,
kuba@kernel.org, linmiaohe@huawei.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in io_commit_cqring (2)
Date: Mon, 29 Mar 2021 04:28:05 -0700 [thread overview]
Message-ID: <000000000000e7989c05beab2c46@google.com> (raw)
In-Reply-To: <000000000000cefea605bea7e8c3@google.com>
syzbot has bisected this issue to:
commit f9d6725bf44a5b9412b5da07e3467100fe2af236
Author: Alexander Lobakin <alobakin@pm.me>
Date: Sat Feb 13 14:11:50 2021 +0000
skbuff: use __build_skb_around() in __alloc_skb()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11934b3ad00000
start commit: 81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13934b3ad00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15934b3ad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=daeff30c2474a60f
dashboard link: https://syzkaller.appspot.com/bug?extid=0e905eb8228070c457a0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e0ed06d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1144754ed00000
Reported-by: syzbot+0e905eb8228070c457a0@syzkaller.appspotmail.com
Fixes: f9d6725bf44a ("skbuff: use __build_skb_around() in __alloc_skb()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2021-03-29 11:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000cefea605bea7e8c3@google.com>]
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=000000000000e7989c05beab2c46@google.com \
--to=syzbot+0e905eb8228070c457a0@syzkaller.appspotmail.com \
--cc=alobakin@pm.me \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=gnault@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@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).