[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b03af88f-8f18-bdac-ae64-c3c0688008d3@gmail.com>
Date: Wed, 7 Nov 2018 22:13:37 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: soukjin.bae@...sung.com,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: (2) (2) [Kernel][NET] Bug report on packet defragmenting
On 11/07/2018 08:26 PM, Eric Dumazet wrote:
>
>
> On 11/07/2018 08:10 PM, 배석진 wrote:
>>> --------- Original Message ---------
>>> Sender : Eric Dumazet <eric.dumazet@...il.com>
>>> Date : 2018-11-08 12:57 (GMT+9)
>>> Title : Re: (2) [Kernel][NET] Bug report on packet defragmenting
>>>
>>> On 11/07/2018 07:24 PM, Eric Dumazet wrote:
>>>
>>>> Sure, it is better if RPS is smarter, but if there is a bug in IPv6 defrag unit
>>>> we must investigate and root-cause it.
>>>
>>> BTW, IPv4 defrag seems to have the same issue.
>>
>>
>> yes, it could be.
>> key point isn't limitted to ipv6.
>>
>> maybe because of faster air-network and modem,
>> it looks like occure more often and we got recognized that.
>>
>> anyway,
>> we'll apply our patch to resolve this problem.
>
> Yeah, and I will fix the defrag units.
>
> We can not rely on other layers doing proper no-reorder logic for us.
>
> Problem here is that multiple cpus attempt concurrent rhashtable_insert_fast()
> and do not properly recover in case -EEXIST is returned.
>
> This is silly, of course :/
Patch would be https://patchwork.ozlabs.org/patch/994658/
Powered by blists - more mailing lists