[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AAFABD0F-C66F-44C2-8BDC-FB489EA8655F@guavus.com>
Date: Tue, 11 May 2010 04:08:30 +0000
From: Bijay Singh <Bijay.Singh@...vus.com>
To: Eric Dumazet <eric.dumazet@...il.com>
CC: Stephen Hemminger <shemminger@...tta.com>,
David Miller <davem@...emloft.net>,
"<bhaskie@...il.com>" <bhaskie@...il.com>,
"<bhutchings@...arflare.com>" <bhutchings@...arflare.com>,
"<netdev@...r.kernel.org>" <netdev@...r.kernel.org>
Subject: Re: TCP-MD5 checksum failure on x86_64 SMP
Hi Eric,
I guess that makes me the enviable one. So I am keen to test out this feature completely, as long as I know what to do as a next step, directions, patches.
Thanks,
Bijay
On 10-May-2010, at 8:48 PM, Eric Dumazet wrote:
> Le lundi 10 mai 2010 à 14:55 +0000, Bijay Singh a écrit :
>> Hi,
>> I had noticed the corruption in the context and actually did what is mentioned.
>>
>> I allocated the context on the stack and plugged in the md5.c functions. I was able to temporarily solve the problem, all this before I got a response on this thread.
>>
>> But now I have seeing another problem, when i change the MTU on the interface from 1500 to 4470 none of the message from the peer get thru and I get hash failed message. I am wondering if this is another bug getting hit in this scenario.
>
> Thats very fine, but you mix very different problems.
>
> Step by step resolution is required, and clean patches too, because
> plugging md5.c functions is not an option for stable series :)
>
> Obviously, nobody seriously used TCP-MD5 on linux, but you...
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists