From: syzbot <syzbot+fbe81b56f7df4c0fb21b@syzkaller.appspotmail.com>
To: andriin@fb.com, 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,
jbaron@akamai.com, john.fastabend@gmail.com, kafai@fb.com,
kuba@kernel.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
ncardwell@google.com, netdev@vger.kernel.org, shuah@kernel.org,
soheil@google.com, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING in sk_stream_kill_queues (4)
Date: Mon, 30 Mar 2020 00:25:03 -0700 [thread overview]
Message-ID: <0000000000007effb905a20d5904@google.com> (raw)
In-Reply-To: <000000000000aa9a23059f62246a@google.com>
syzbot suspects this bug was fixed by commit:
commit b6f6118901d1e867ac9177bbff3b00b185bd4fdc
Author: Eric Dumazet <edumazet@google.com>
Date: Tue Feb 25 19:52:29 2020 +0000
ipv6: restrict IPV6_ADDRFORM operation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1177dc25e00000
start commit: f8788d86 Linux 5.6-rc3
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9833e26bab355358
dashboard link: https://syzkaller.appspot.com/bug?extid=fbe81b56f7df4c0fb21b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fd92c3e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11679a81e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: ipv6: restrict IPV6_ADDRFORM operation
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-03-30 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 8:19 WARNING in sk_stream_kill_queues (4) syzbot
2020-03-30 7:25 ` syzbot [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=0000000000007effb905a20d5904@google.com \
--to=syzbot+fbe81b56f7df4c0fb21b@syzkaller.appspotmail.com \
--cc=andriin@fb.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=jbaron@akamai.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=soheil@google.com \
--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 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.