From: David Miller <davem@davemloft.net>
To: ebiggers@kernel.org
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 11:12:25 -0700 (PDT) [thread overview]
Message-ID: <20190724.111225.2257475150626507655.davem@davemloft.net> (raw)
In-Reply-To: <20190724163014.GC673@sol.localdomain>
From: Eric Biggers <ebiggers@kernel.org>
Date: Wed, 24 Jul 2019 09:30:14 -0700
> On Wed, Jul 24, 2019 at 08:39:05AM +0200, Eric Dumazet wrote:
>> 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.
>>
>
> First, based on experience, I'd guess about 30-45 of these are still valid. 17
> were seen in mainline in the last week, but some others are valid too. The ones
> most likely to still be valid are at the beginning of the list. So let's try
> not use the presence of outdated bugs as an excuse not to fix current bugs.
So about half of the bugs we are to look at are already fixed and thus
noise, even as estimated by you.
I agree with Eric, these "reminders" are bad for the people you
actually want to work on fixing these bugs.
> Since the kernel community is basically in continuous bug bankruptcy and lots of
I don't like this hyperbole. Please present facts and information we
can actually use to improve the kernel development and bug fixing
process.
Thank you.
next prev parent reply other threads:[~2019-07-24 18:12 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 [this message]
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=20190724.111225.2257475150626507655.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--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).