From: syzbot <syzbot+5013d47539cdd43e7098@syzkaller.appspotmail.com>
To: ast@kernel.org, aviadye@mellanox.com, borisp@mellanox.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davejwatson@fb.com,
davem@davemloft.net, edumazet@google.com, eranbe@mellanox.com,
eric.dumazet@gmail.com, john.fastabend@gmail.com, kafai@fb.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: Re: kernel BUG at include/linux/mm.h:LINE! (5)
Date: Mon, 11 Mar 2019 06:23:01 -0700 [thread overview]
Message-ID: <000000000000c66d400583d17848@google.com> (raw)
In-Reply-To: <00000000000054cc6d05834c33d7@google.com>
syzbot has bisected this bug to:
commit 94850257cf0f88b20db7644f28bfedc7d284de15
Author: Boris Pismenny <borisp@mellanox.com>
Date: Wed Feb 27 15:38:03 2019 +0000
tls: Fix tls_device handling of partial records
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d9d977200000
start commit: 94850257 tls: Fix tls_device handling of partial records
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=1039d977200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17d9d977200000
kernel config: https://syzkaller.appspot.com/x/.config?x=47f2db597668ac40
dashboard link: https://syzkaller.appspot.com/bug?extid=5013d47539cdd43e7098
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148763eb200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1416ff3d200000
Reported-by: syzbot+5013d47539cdd43e7098@syzkaller.appspotmail.com
Fixes: 94850257 ("tls: Fix tls_device handling of partial records")
next prev parent reply other threads:[~2019-03-11 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 22:23 kernel BUG at include/linux/mm.h:LINE! (5) syzbot
2019-03-05 17:54 ` Eric Dumazet
2019-03-11 13:23 ` syzbot [this message]
2019-12-06 10:14 ` syzbot
2019-12-06 17:58 ` 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=000000000000c66d400583d17848@google.com \
--to=syzbot+5013d47539cdd43e7098@syzkaller.appspotmail.com \
--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=edumazet@google.com \
--cc=eranbe@mellanox.com \
--cc=eric.dumazet@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.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 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).