From: syzbot <syzbot+0b3ccd4f62dac2cf3a7d@syzkaller.appspotmail.com>
To: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
edumazet@google.com, john.fastabend@gmail.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: general protection fault in tcp_cleanup_ulp
Date: Fri, 29 Mar 2019 22:17:01 -0700 [thread overview]
Message-ID: <000000000000b4d871058548e5c8@google.com> (raw)
In-Reply-To: <00000000000006602605752ffa1a@google.com>
syzbot has bisected this bug to:
commit 90545cdc3f2b2ea700e24335610cd181e73756da
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu Aug 16 19:49:07 2018 +0000
tcp, ulp: fix leftover icsk_ulp_ops preventing sock from reattach
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15dab897200000
start commit: 28619527 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: bpf
final crash: https://syzkaller.appspot.com/x/report.txt?x=17dab897200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13dab897200000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
dashboard link: https://syzkaller.appspot.com/bug?extid=0b3ccd4f62dac2cf3a7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13537269400000
Reported-by: syzbot+0b3ccd4f62dac2cf3a7d@syzkaller.appspotmail.com
Fixes: 90545cdc3f2b ("tcp, ulp: fix leftover icsk_ulp_ops preventing sock
from reattach")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-30 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 8:50 general protection fault in tcp_cleanup_ulp syzbot
2018-09-12 10:00 ` syzbot
2019-03-30 5:17 ` syzbot [this message]
2019-11-07 13:42 ` syzbot
2019-11-13 16:50 ` John Fastabend
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=000000000000b4d871058548e5c8@google.com \
--to=syzbot+0b3ccd4f62dac2cf3a7d@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.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=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 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.