From: Eric Dumazet <eric.dumazet@gmail.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Florian Westphal <fw@strlen.de>,
Ilya Maximets <i.maximets@samsung.com>,
Eric Dumazet <edumazet@google.com>,
David Ahern <dsahern@gmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 99 open syzbot bugs in net subsystem
Date: Wed, 24 Jul 2019 08:39:05 +0200 [thread overview]
Message-ID: <63f12327-dd4b-5210-4de2-705af6bc4ba4@gmail.com> (raw)
In-Reply-To: <20190724013813.GB643@sol.localdomain>
On 7/24/19 3:38 AM, Eric Biggers wrote:
> [This email was generated by a script. Let me know if you have any suggestions
> to make it better, or if you want it re-generated with the latest status.]
>
> Of the currently open syzbot reports against the upstream kernel, I've manually
> marked 99 of them as possibly being bugs in the net subsystem. This category
> only includes the networking bugs that I couldn't assign to a more specific
> component (bpf, xfrm, bluetooth, tls, tipc, sctp, wireless, etc.). I've listed
> these reports below, sorted by an algorithm that tries to list first the reports
> most likely to be still valid, important, and actionable.
>
> Of these 99 bugs, 17 were seen in mainline in the last week.
>
> Of these 99 bugs, 4 were bisected to commits from the following people:
>
> Florian Westphal <fw@strlen.de>
> Ilya Maximets <i.maximets@samsung.com>
> Eric Dumazet <edumazet@google.com>
> David Ahern <dsahern@gmail.com>
>
> If you believe a bug is no longer valid, please close the syzbot report by
> sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the
> original thread, as explained at https://goo.gl/tpsmEJ#status
>
> If you believe I misattributed a bug to the net subsystem, please let me know,
> and if possible forward the report to the correct people or mailing list.
>
Some of the bugs have been fixed already, before syzbot found them.
Why force human to be gentle to bots and actually replying to them ?
I usually simply wait that syzbot is finding the bug does not repro anymore,
but now if you send these emails, we will have even more pressure on us.
next prev parent reply other threads:[~2019-07-24 6:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 1:38 Reminder: 99 open syzbot bugs in net subsystem Eric Biggers
2019-07-24 6:39 ` Eric Dumazet [this message]
2019-07-24 16:30 ` Eric Biggers
2019-07-24 18:12 ` David Miller
2019-07-24 18:37 ` Eric Biggers
2019-07-24 18:52 ` Eric Dumazet
2019-07-24 19:03 ` Eric Biggers
2019-07-24 20:09 ` David Miller
2019-07-24 21:09 ` Eric Biggers
2019-07-25 5:04 ` Eric Dumazet
2019-07-31 2:57 ` Eric Biggers
2019-07-31 15:13 ` David Ahern
2019-07-25 3:39 ` Theodore Y. Ts'o
2019-07-25 4:40 ` Eric Biggers
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=63f12327-dd4b-5210-4de2-705af6bc4ba4@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=i.maximets@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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 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).