From: Eric Biggers <ebiggers@kernel.org>
To: Vakul Garg <vakul.garg@nxp.com>
Cc: syzbot <syzbot+df0d4ec12332661dd1f9@syzkaller.appspotmail.com>,
ast@kernel.org, aviadye@mellanox.com, borisp@mellanox.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davejwatson@fb.com,
davem@davemloft.net, john.fastabend@gmail.com, kafai@fb.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com
Subject: Re: kernel BUG at include/linux/scatterlist.h:LINE!
Date: Mon, 10 Jun 2019 11:41:04 -0700 [thread overview]
Message-ID: <20190610184103.GF63833@gmail.com> (raw)
In-Reply-To: <000000000000f41cd905897c075e@google.com>
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
>
> The bug was bisected to:
>
> commit f295b3ae9f5927e084bd5decdff82390e3471801
> Author: Vakul Garg <vakul.garg@nxp.com>
> Date: Wed Mar 20 02:03:36 2019 +0000
>
> net/tls: Add support of AES128-CCM based ciphers
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16915282a00000
> final crash: https://syzkaller.appspot.com/x/report.txt?x=15915282a00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11915282a00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+df0d4ec12332661dd1f9@syzkaller.appspotmail.com
> Fixes: f295b3ae9f59 ("net/tls: Add support of AES128-CCM based ciphers")
>
> ------------[ cut here ]------------
> kernel BUG at include/linux/scatterlist.h:97!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 8868 Comm: syz-executor428 Not tainted 5.2.0-rc1+ #21
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
> Google 01/01/2011
> RIP: 0010:sg_assign_page include/linux/scatterlist.h:97 [inline]
> RIP: 0010:sg_set_page include/linux/scatterlist.h:119 [inline]
> RIP: 0010:sk_msg_page_add include/linux/skmsg.h:246 [inline]
> RIP: 0010:tls_sw_do_sendpage net/tls/tls_sw.c:1171 [inline]
> RIP: 0010:tls_sw_sendpage+0xd63/0xf50 net/tls/tls_sw.c:1230
Hi Vakul, when are you planning to fix this?
- Eric
next prev parent reply other threads:[~2019-06-10 18:41 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 [this message]
2019-11-19 4:57 ` [net/tls] " Eric Biggers
2019-11-19 20:30 ` Jakub Kicinski
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=20190610184103.GF63833@gmail.com \
--to=ebiggers@kernel.org \
--cc=ast@kernel.org \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+df0d4ec12332661dd1f9@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vakul.garg@nxp.com \
--cc=yhs@fb.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 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.