[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191108.113527.2242883926552730503.davem@davemloft.net>
Date: Fri, 08 Nov 2019 11:35:27 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: gregkh@...uxfoundation.org
Cc: jwi@...ux.ibm.com, sashal@...nel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, linux-s390@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 204/205] s390/qeth: limit csum offload
erratum to L3 devices
From: Greg KH <gregkh@...uxfoundation.org>
Date: Fri, 8 Nov 2019 13:34:16 +0100
> On Fri, Nov 08, 2019 at 01:16:26PM +0100, Julian Wiedmann wrote:
>> On 08.11.19 13:00, Sasha Levin wrote:
>> > On Fri, Nov 08, 2019 at 12:50:24PM +0100, Julian Wiedmann wrote:
>> >> On 08.11.19 12:37, Sasha Levin wrote:
>> >>> From: Julian Wiedmann <jwi@...ux.ibm.com>
>> >>>
>> >>> [ Upstream commit f231dc9dbd789b0f98a15941e3cebedb4ad72ad5 ]
>> >>>
>> >>> Combined L3+L4 csum offload is only required for some L3 HW. So for
>> >>> L2 devices, don't offload the IP header csum calculation.
>> >>>
>> >>
>> >> NACK, this has no relevance for stable.
>> >
>> > Sure, I'll drop it.
>> >
>> > Do you have an idea why the centos and ubuntu folks might have
>> > backported this commit into their kernels?
>> >
>>
>> No clue, I trust they have their own reasons.
>>
>
> I cant see centos backporting anything unless they were asked to do so.
> And this really looks like a "bugfix" to me, why isn't this relevant for
> any older kernel versions?
Yeah seriously, this looks entirely legit.
Powered by blists - more mailing lists