From: Cong Wang <amwang@redhat.com>
To: Jesse Gross <jesse@nicira.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next] openvswitch: adjust skb_gso_segment() for rx path
Date: Fri, 01 Feb 2013 10:09:04 +0800 [thread overview]
Message-ID: <1359684544.22074.6.camel@cr0> (raw)
In-Reply-To: <CAEP_g=9JqFi7apps-aDqxuGck-hYSvaUT6pzXR-gDkAvLovS8A@mail.gmail.com>
On Thu, 2013-01-31 at 17:09 -0800, Jesse Gross wrote:
>
> I would argue that the meanings are the same on transmit and receive
> but the values that you are likely to see differ depending on the
> path. With bridging (which includes both Open vSwitch and the bridge)
> it's very difficult to know whether you are on the transmit or receive
> path. Personally, I would just remove the warning completely.
I would keep it as it is, I fixed several RHEL kernel bugs exposed by
this warning, it is pretty useful for debugging.
...
>
> You can just drop the change in the block above and gso_send_check()
> will take care of the rest. Regardless of the state of the incoming
> packet, GSO needs the checksum to be reset to CHECKSUM_PARTIAL in
> order to work.
Right, makes sense.
>
> I think this is a different problem, unrelated to the checksum issue.
> Can you test this patch:
> http://git.kernel.org/?p=linux/kernel/git/jesse/openvswitch.git;a=commit;h=d9d59089c43fc33eb403cbb928e56c131f191dd5
>
> I believe it should fix the problem, although there are still a few
> lingering reports that I'm trying to track down.
I will try your patch together with my updated patch.
Thanks!
next prev parent reply other threads:[~2013-02-01 2:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 8:38 [Patch net-next] openvswitch: adjust skb_gso_segment() for rx path Cong Wang
2013-01-30 21:54 ` Jesse Gross
2013-01-31 1:48 ` Cong Wang
2013-02-01 1:09 ` Jesse Gross
2013-02-01 2:09 ` Cong Wang [this message]
2013-02-06 2:36 ` Cong Wang
2013-01-31 3:46 ` David Miller
2013-01-31 8:31 ` Cong Wang
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=1359684544.22074.6.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.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).