On Mon, Mar 19, 2018 at 10:16 AM Eric Dumazet
wrote:
> On 03/19/2018 07:03 AM, David Miller wrote:
> > From: Eric Dumazet
> > Date: Mon, 19 Mar 2018 05:17:37 -0700
> >
> >> We have sent a fix last week, I am not sure if David took it.
> >>
> >> https://patchwork.ozlabs.org/patch/886324/
> >
>
On 03/19/2018 07:03 AM, David Miller wrote:
> From: Eric Dumazet
> Date: Mon, 19 Mar 2018 05:17:37 -0700
>
>> We have sent a fix last week, I am not sure if David took it.
>>
>> https://patchwork.ozlabs.org/patch/886324/
>
> I thought I submitted that in my last round of -stable submissions,
>
From: Eric Dumazet
Date: Mon, 19 Mar 2018 05:17:37 -0700
> We have sent a fix last week, I am not sure if David took it.
>
> https://patchwork.ozlabs.org/patch/886324/
I thought I submitted that in my last round of -stable submissions,
but I have re-added this to my stable queue and will make s
2018-03-19 12:51 GMT+01:00 Tomas Charvat :
> I have seen on multiple servers with kernel-4.14.26 and 4.14.27
> following errors in dmes. It seems that it also caused involved process
> to crash (apache and qmail-smtpd).
Hi,
upsteam has a fix for it:
https://www.mail-archive.com/netdev@vger.kernel.
On 03/19/2018 04:51 AM, Tomas Charvat wrote:
> I have seen on multiple servers with kernel-4.14.26 and 4.14.27
> following errors in dmes. It seems that it also caused involved process
> to crash (apache and qmail-smtpd).
>
> [Fri Mar 16 00:00:11 2018] BUG: unable to handle kernel NULL pointer
>
I have seen on multiple servers with kernel-4.14.26 and 4.14.27
following errors in dmes. It seems that it also caused involved process
to crash (apache and qmail-smtpd).
[Fri Mar 16 00:00:11 2018] BUG: unable to handle kernel NULL pointer
dereference at 0038
[Fri Mar 16 00:00:11 2018]
