From: Eric Dumazet <eric.dumazet@gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>, netdev@vger.kernel.org
Subject: Re: CVE-2019-11683
Date: Sat, 4 May 2019 12:43:23 -0400 [thread overview]
Message-ID: <b29aea5d-930e-778a-1627-1bfd85cbe849@gmail.com> (raw)
In-Reply-To: <65007ac9-97f2-425e-66f4-3b552deb20ac@thelounge.net>
On 5/4/19 12:39 PM, Reindl Harald wrote:
>
>
> Am 04.05.19 um 18:32 schrieb Eric Dumazet:
>> On 5/4/19 12:13 PM, Reindl Harald wrote:
>>>
>>> ok, so the answer is no
>>>
>>> what's the point then release every 2 days a new "stable" kernel?
>>> even distributions like Fedora are not able to cope with that
>>
>> That is a question for distros, not for netdev@ ?
>
> maybe, but the point is that we go in a direction where you have every 2
> or 3 days a "stable" update up to days where at 9:00 AM a "stable" point
> release appears at kernel.org and one hour later the next one from Linus
> himself to fix a regression in the release an hour ago
>
> release-realy-release-often is fine, but that smells like rush and
> nobody downstream be it a sysadmin or a distribution can cope with that
> when you are in a testing stage a while start deploy there are 2 new
> releases with a long changelog
>
> just because you never know if what you intended to deploy now better
> should be skipped or joust go ahead because the next one a few days
> later brings a regression and which ones are the regressions adn which
> ones are the fixes which for me personally now leads to just randomly
> update every few weaks
>
In any case, this discussion has nothing to do with netdev@
Are you suggesting that we should not fix bugs at given period of times,
just because a 'release of some stable kernel' happened one day before ?
How you do your updates does not really concern us, sorry !
next prev parent reply other threads:[~2019-05-04 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 15:49 CVE-2019-11683 Reindl Harald
2019-05-04 16:06 ` CVE-2019-11683 Eric Dumazet
2019-05-04 16:13 ` CVE-2019-11683 Reindl Harald
2019-05-04 16:32 ` CVE-2019-11683 Eric Dumazet
2019-05-04 16:39 ` CVE-2019-11683 Reindl Harald
2019-05-04 16:42 ` CVE-2019-11683 Stephen Hemminger
2019-05-04 16:43 ` Eric Dumazet [this message]
2019-05-04 16:47 ` CVE-2019-11683 Reindl Harald
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=b29aea5d-930e-778a-1627-1bfd85cbe849@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=h.reindl@thelounge.net \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox