From: John Fastabend <john.fastabend@gmail.com>
To: syzbot <syzbot+0b3ccd4f62dac2cf3a7d@syzkaller.appspotmail.com>,
ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, edumazet@google.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: general protection fault in tcp_cleanup_ulp
Date: Wed, 13 Nov 2019 08:50:51 -0800 [thread overview]
Message-ID: <5dcc346b151ef_65172b2715e085b42b@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <000000000000f90bb30596c1d438@google.com>
syzbot wrote:
> syzbot suspects this bug was fixed by commit:
>
> commit 5607fff303636d48b88414c6be353d9fed700af2
> Author: John Fastabend <john.fastabend@gmail.com>
> Date: Tue Sep 18 16:01:44 2018 +0000
>
> bpf: sockmap only allow ESTABLISHED sock state
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17fdc73c600000
> start commit: 28619527 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> git tree: bpf
> 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
>
> If the result looks correct, please mark the bug fixed by replying with:
>
> #syz fix: bpf: sockmap only allow ESTABLISHED sock state
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: bpf: sockmap only allow ESTABLISHED sock state
prev parent reply other threads:[~2019-11-13 16:51 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
2019-11-07 13:42 ` syzbot
2019-11-13 16:50 ` John Fastabend [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=5dcc346b151ef_65172b2715e085b42b@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=syzbot+0b3ccd4f62dac2cf3a7d@syzkaller.appspotmail.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 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.