From: "wei zhang" <asuka.com@163.com>
To: "Jesse Gross" <jesse@nicira.com>
Cc: "David Miller" <davem@davemloft.net>,
"dev@openvswitch.org" <dev@openvswitch.org>,
netdev <netdev@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] openvswitch: supply a dummy err_handler of gre_cisco_protocol to prevent kernel crash
Date: Wed, 2 Apr 2014 08:23:28 +0800 (CST) [thread overview]
Message-ID: <158d7617.12955.1451fd1b702.Coremail.asuka.com@163.com> (raw)
In-Reply-To: <CAEP_g=-an14xN7Q2fmC+wMk1G9WTAX+JrVeBx5QGnw2-XU3ezQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2365 bytes --]
At 2014-04-02 02:27:56,"Jesse Gross" <jesse@nicira.com> wrote:
>On Tue, Apr 1, 2014 at 8:24 AM, wei zhang <asuka.com@163.com> wrote:
>> At 2014-04-01 08:49:53,"Jesse Gross" <jesse@nicira.com> wrote:
>>>On Sun, Mar 30, 2014 at 5:12 AM, wei zhang <asuka.com@163.com> wrote:
>>>> At 2014-03-29 06:02:25,"Jesse Gross" <jesse@nicira.com> wrote:
>>
>>>> Maybe I misunderstand something? I think if we discard all packet pass to us
>>>> when we use gre vport, new gre_cisco_protocol which has lower priority could
>>>> not see the packet intended to it.
>>>
>>>That's true but in this case it would also not see any data packets,
>>>so I don't think that situation would work well anyways.
>>>
>>>> I checked the implementation of the ipgre_err(), which has be called before
>>>> the err_handler of gre vport. It use the the (local address, remote address, key)
>>>> to distinguish the packet which is realy intended to it, although it could not
>>>> always get the key from the icmp packet. Should we do as the same as it?
>>>> I'm not sure this is feasible, any advice is appreciate.
>>>
>>>OVS does flow based matching rather than using a static set of
>>>configuration parameters, so everything "matches" in some way
>>>(although the result might be to drop).
>>
>> So the flow based match could dynamically determine by the ovs daemon, we could
>> not find out the belonging of the packet as far as we call ovs_dp_upcall(), isn't it?
>
>That's right - and since the OVS flow table always has a default
>behavior (even if it is drop or send to controller) there's never a
>packet that isn't considered to be destined to OVS once it is
>received.
>
>If this makes sense to you, would you mind submitting the patch you
>had earlier formally with a commit message and signed off by line?
Sure, thank you again as it's my first time to send patch to the kernel, your patient and kind
help give me confidence to do it :)
Regards,
Wei Zhangÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2014-04-02 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1395957398-24546-1-git-send-email-asuka.com@163.com>
2014-03-28 22:02 ` Jesse Gross
2014-03-30 12:12 ` wei zhang
2014-04-01 0:49 ` Jesse Gross
2014-04-01 15:24 ` wei zhang
2014-04-01 18:27 ` Jesse Gross
2014-04-02 0:23 ` wei zhang [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=158d7617.12955.1451fd1b702.Coremail.asuka.com@163.com \
--to=asuka.com@163.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome