From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Boris Pismenny <borisp@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
syzbot <syzbot+df0d4ec12332661dd1f9@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com, netdev@vger.kernel.org
Subject: Re: [net/tls] kernel BUG at include/linux/scatterlist.h:LINE!
Date: Tue, 19 Nov 2019 12:30:39 -0800 [thread overview]
Message-ID: <20191119123039.64dca58d@cakuba.netronome.com> (raw)
In-Reply-To: <20191119045707.GI163020@sol.localdomain>
On Mon, 18 Nov 2019 20:57:07 -0800, Eric Biggers wrote:
> On Wed, May 22, 2019 at 08:58:05AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit: af8f3fb7 net: stmmac: dma channel control register need to..
> > git tree: net
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17c2d418a00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=fc045131472947d7
> > dashboard link: https://syzkaller.appspot.com/bug?extid=df0d4ec12332661dd1f9
> > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b53ce4a00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b0aa52a00000
>
> This looks like a TLS bug that is still valid. Can you please look into it?
> Here's the same crash from net-next today (commit 19b7e21c55c8):
> https://syzkaller.appspot.com/text?tag=CrashReport&x=16380c6ae00000
Thanks for brining it up, I should be able to get to it in the next
two days.
prev parent reply other threads:[~2019-11-19 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 15:58 kernel BUG at include/linux/scatterlist.h:LINE! syzbot
2019-06-10 18:41 ` Eric Biggers
2019-11-19 4:57 ` [net/tls] " Eric Biggers
2019-11-19 20:30 ` Jakub Kicinski [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=20191119123039.64dca58d@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=ebiggers@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+df0d4ec12332661dd1f9@syzkaller.appspotmail.com \
--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).