Am 04.05.19 um 18:43 schrieb Eric Dumazet:
> 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?
sorry to get cynical but that's likely
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 cop
On Sat, 4 May 2019 18:39:15 +0200
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
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 fo
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@ ?
Am 04.05.19 um 18:06 schrieb Eric Dumazet:
>> --
>>
>> https://www.openwall.com/lists/oss-security/2019/05/02/1
>>
>> syzbot has reported a remotely triggerable memory corruption in the
>> Linux kernel. It's been introduced quite recently in e20cf8d3f1f7
>> ("udp: implement G
On 5/4/19 11:49 AM, Reindl Harald wrote:
> is this fixed in 5.0.12 and just not visible in the changelog?
>
> because if not there's no poiunt to reboot a over a long time randomly
> crahsing firewall setup which *appears* stable now after replace "LOG"
> with "NFLOG" and remove --reap from the
