From: "Jonathan M. McCune" <jmmccune@ece.cmu.edu>
To: Nivedita Singhvi <nsnix@comcast.net>
Cc: xen-devel@lists.xensource.com, caceres@us.ibm.com,
"Jonathan M. McCune" <jonmccune@cmu.edu>,
jaegert@us.ibm.com, sailer@us.ibm.com
Subject: Re: Xen checksumming bug with IPsec ESP packets
Date: Thu, 04 Aug 2005 21:06:27 -0400 [thread overview]
Message-ID: <42F2BB93.7020005@ece.cmu.edu> (raw)
In-Reply-To: <42F2BAD6.3020400@comcast.net>
I can test patches until the end of August.
Cheers,
-Jon
Nivedita Singhvi wrote:
> Keir Fraser wrote:
>
>>
>> On 3 Aug 2005, at 17:27, Jonathan M. McCune wrote:
>>
>>> We fixed this by removing the addition of flag NETIF_F_IP_CSUM in
>>> drivers/xen/netfront/netfront.c:create_netdev(). I believe this
>>> tells the kernel to just always do the checksum in software. Thus,
>>> the broken optimization for TCP/UDP packets gets bypassed.
>>>
>>>
>>> Permanent Solution:
>>>
>>> ???
>>>
>>> That's why I posted this message... :-)
>>
>>
>>
>> I suspect the ESP code would need to be made aware of the csum_blank
>> field, and fill in before forwarding. There are doubtless other paths
>> that may need similar tweaks (e.g., NAT IP masquerading is untested I
>> think, although there's a fair chance it'll just work).
>>
>> Apart from the above 'proper fix', simple not-so-hacky solutions
>> include:
>> * Run 'ethtool -K tx off' in each domU
>> * Add an option to netback in domain0 to fill in checksums itself if
>> not done by domU.
>> * Allow netback to advertise to domUs whether it accepts
>> non-checksummed packets, and have an option to set this advertisement
>> when you start netback.
>
>
> Keir, Jonathan,
>
> I stuck the above in a bugzilla entry (#143) just for better
> tracking. Jonathan, would you be able to test patches?
>
> thanks,
> Nivedita
prev parent reply other threads:[~2005-08-05 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 16:27 Xen checksumming bug with IPsec ESP packets Jonathan M. McCune
2005-08-03 17:01 ` Keir Fraser
2005-08-05 1:03 ` Nivedita Singhvi
2005-08-05 1:06 ` Jonathan M. McCune [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42F2BB93.7020005@ece.cmu.edu \
--to=jmmccune@ece.cmu.edu \
--cc=caceres@us.ibm.com \
--cc=jaegert@us.ibm.com \
--cc=jonmccune@cmu.edu \
--cc=nsnix@comcast.net \
--cc=sailer@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.