From: syzbot <syzbot+66e3ea42c4b176748b9c@syzkaller.appspotmail.com>
To: aviadye@mellanox.com, borisp@mellanox.com, bp@alien8.de,
daniel@iogearbox.net, davem@davemloft.net, ebiggers@kernel.org,
herbert@gondor.apana.org.au, hpa@zytor.com,
john.fastabend@gmail.com, kuba@kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
liujian56@huawei.com, mingo@redhat.com, netdev@vger.kernel.org,
pabeni@redhat.com, sd@queasysnail.net,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vfedorenko@novek.ru, x86@kernel.org
Subject: Re: [syzbot] [net] [crypto] general protection fault in scatterwalk_copychunks (4)
Date: Thu, 12 Oct 2023 14:25:30 -0700 [thread overview]
Message-ID: <0000000000004b2b3d06078b94b0@google.com> (raw)
In-Reply-To: <00000000000006e7be05bda1c084@google.com>
syzbot suspects this issue was fixed by commit:
commit cfaa80c91f6f99b9342b6557f0f0e1143e434066
Author: Liu Jian <liujian56@huawei.com>
Date: Sat Sep 9 08:14:34 2023 +0000
net/tls: do not free tls_rec on async operation in bpf_exec_tx_verdict()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17338965680000
start commit: bd6c11bc43c4 Merge tag 'net-next-6.6' of git://git.kernel...
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=634e05b4025da9da
dashboard link: https://syzkaller.appspot.com/bug?extid=66e3ea42c4b176748b9c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10160198680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15feabc0680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/tls: do not free tls_rec on async operation in bpf_exec_tx_verdict()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-12 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 6:48 [syzbot] general protection fault in scatterwalk_copychunks (4) syzbot
2021-08-13 10:03 ` syzbot
2021-08-14 13:07 ` syzbot
2023-10-12 21:25 ` syzbot [this message]
2023-10-13 8:49 ` [syzbot] [net] [crypto] " Sabrina Dubroca
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=0000000000004b2b3d06078b94b0@google.com \
--to=syzbot+66e3ea42c4b176748b9c@syzkaller.appspotmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=bp@alien8.de \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liujian56@huawei.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vfedorenko@novek.ru \
--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 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.