From: Roi Dayan <roid@nvidia.com>
To: patchwork-bot+netdevbpf@kernel.org, Toms Atteka <cpp.code.lv@gmail.com>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kuba@kernel.org,
davem@davemloft.net
Subject: Re: [ovs-dev] [PATCH net-next v8] net: openvswitch: IPv6: Add IPv6 extension header support
Date: Wed, 2 Mar 2022 12:03:49 +0200 [thread overview]
Message-ID: <3adf00c7-fe65-3ef4-b6d7-6d8a0cad8a5f@nvidia.com> (raw)
In-Reply-To: <164578561098.13834.14017896440355101001.git-patchwork-notify@kernel.org>
On 2022-02-25 12:40 PM, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This patch was applied to netdev/net-next.git (master)
> by David S. Miller <davem@davemloft.net>:
>
> On Wed, 23 Feb 2022 16:54:09 -0800 you wrote:
>> This change adds a new OpenFlow field OFPXMT_OFB_IPV6_EXTHDR and
>> packets can be filtered using ipv6_ext flag.
>>
>> Signed-off-by: Toms Atteka <cpp.code.lv@gmail.com>
>> Acked-by: Pravin B Shelar <pshelar@ovn.org>
>> ---
>> include/uapi/linux/openvswitch.h | 6 ++
>> net/openvswitch/flow.c | 140 +++++++++++++++++++++++++++++++
>> net/openvswitch/flow.h | 14 ++++
>> net/openvswitch/flow_netlink.c | 26 +++++-
>> 4 files changed, 184 insertions(+), 2 deletions(-)
>
> Here is the summary with links:
> - [net-next,v8] net: openvswitch: IPv6: Add IPv6 extension header support
> https://git.kernel.org/netdev/net-next/c/28a3f0601727
>
> You are awesome, thank you!
Hi,
After the merge of this patch I fail to do ipv6 traffic in ovs.
Am I missing something?
ovs-vswitchd.log has this msg
2022-03-02T09:52:26.604Z|00013|odp_util(handler1)|WARN|attribute
packet_type has length 2 but should have length 4
Thanks,
Roi
next prev parent reply other threads:[~2022-03-02 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:54 [PATCH net-next v8] net: openvswitch: IPv6: Add IPv6 extension header support Toms Atteka
2022-02-25 10:40 ` patchwork-bot+netdevbpf
2022-03-02 10:03 ` Roi Dayan [this message]
2022-03-02 10:50 ` [ovs-dev] " Roi Dayan
2022-03-02 13:59 ` Eelco Chaudron
2022-03-07 8:49 ` Roi Dayan
2022-03-07 20:26 ` Jakub Kicinski
2022-03-07 22:14 ` Ilya Maximets
2022-03-07 22:46 ` Jakub Kicinski
2022-03-08 0:04 ` Ilya Maximets
2022-03-08 5:45 ` Jakub Kicinski
2022-03-08 8:21 ` Johannes Berg
2022-03-08 14:12 ` Ilya Maximets
2022-03-08 14:39 ` Roi Dayan
2022-03-08 18:25 ` Ilya Maximets
2022-03-08 20:17 ` Jakub Kicinski
2022-03-08 16:17 ` Jakub Kicinski
2022-03-08 19:33 ` Ilya Maximets
2022-03-08 20:16 ` Jakub Kicinski
2022-03-09 7:49 ` Roi Dayan
2022-03-09 13:43 ` Ilya Maximets
2022-03-09 16:17 ` Jakub Kicinski
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=3adf00c7-fe65-3ef4-b6d7-6d8a0cad8a5f@nvidia.com \
--to=roid@nvidia.com \
--cc=cpp.code.lv@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@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).