From: Breno Leitao <leitao@linux.vnet.ibm.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Jay Vosburgh <fubar@us.ibm.com>
Subject: Re: [PATCH] ehea: Fix a checksum issue on the receive path
Date: Fri, 08 Oct 2010 11:14:10 -0300 [thread overview]
Message-ID: <4CAF2732.90703@linux.vnet.ibm.com> (raw)
In-Reply-To: <1286513130.6536.467.camel@edumazet-laptop>
Hi Eric
On 10/08/2010 01:45 AM, Eric Dumazet wrote:
> Just to be clear : packets with wrong checksums are not given to upper
> stack, so a tcpdump can not display them ? I am not sure many drivers do
> that.
Well, what my code does is: 1) if the current packet is a UDP/TCP, then
the checksum is not necessary, since we would check the checksum on
ehea_proc_rwqes(), specific at this part of the code:
if (!ehea_check_cqe(cqe, &rq)) {
// Send the packet to the up layers
And ehea_check_cqe() checks for wrong checksumed packets on:
if ((cqe->status & EHEA_CQE_STAT_ERR_MASK) == 0)
return 0;
Botton line, TCP/UDP packets with wrong checksums are dropped by
ehea_proc_rwqes(), others go to the up layer.
So, back to your question, you are saying that we shouldn't do that,
meaning that we should send to the upper layers all packets ? even those
that have the wrong checksum ?
Thanks
Breno
next prev parent reply other threads:[~2010-10-08 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 23:17 [PATCH] ehea: Fix a checksum issue on the receive path leitao
2010-10-08 4:45 ` Eric Dumazet
2010-10-08 14:14 ` Breno Leitao [this message]
2010-10-08 14:36 ` Eric Dumazet
2010-10-09 16:20 ` David Miller
2010-10-09 17:31 ` Stephen Hemminger
2010-10-13 14:06 ` Breno Leitao
2010-10-13 21:25 ` David Miller
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=4CAF2732.90703@linux.vnet.ibm.com \
--to=leitao@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).