From: Eric Biggers <ebiggers@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, dvyukov@google.com,
netdev@vger.kernel.org, fw@strlen.de, i.maximets@samsung.com,
edumazet@google.com, 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 14:09:51 -0700 [thread overview]
Message-ID: <20190724210950.GH213255@gmail.com> (raw)
In-Reply-To: <20190724.130928.1854327585456756387.davem@davemloft.net>
On Wed, Jul 24, 2019 at 01:09:28PM -0700, David Miller wrote:
> From: Eric Biggers <ebiggers@kernel.org>
> Date: Wed, 24 Jul 2019 11:37:12 -0700
>
> > We can argue about what words to use to describe this situation, but
> > it doesn't change the situation itself.
>
> And we should argue about those words because it matters to humans and
> effects how they feel, and humans ultimately fix these bugs.
>
> So please stop with the hyperbole.
>
> Thank you.
Okay, there are 151 bugs that syzbot saw on the mainline Linux kernel in the
last 7 days (90.1% with reproducers). Of those, 59 were reported over 3 months
ago (89.8% with reproducers). Of those, 12 were reported over a year ago (83.3%
with reproducers).
No opinion on whether those are small/medium/large numbers, in case it would
hurt someone's feelings.
These numbers do *not* include bugs that are still valid but weren't seen on
mainline in last 7 days, e.g.:
- Bugs that are seen only rarely, so by chance weren't seen in last 7 days.
- Bugs only in linux-next and/or subsystem branches.
- Bugs that were seen in mainline more than 7 days ago, and then only on
linux-next or subsystem branch in last 7 days.
- Bugs that stopped being seen due to a change in syzkaller.
- Bugs that stopped being seen due to a change in kernel config.
- Bugs that stopped being seen due to other environment changes such as kernel
command line parameters.
- Bugs that stopped being seen due to a kernel change that hid the bug but
didn't actually fix it, i.e. still reachable in other ways.
Eric
next prev parent reply other threads:[~2019-07-24 21:09 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
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 [this message]
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=20190724210950.GH213255@gmail.com \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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).