From: David Miller <davem@redhat.com>
To: gvaradar@cisco.com
Cc: netdev@vger.kernel.org, benve@cisco.com
Subject: Re: [PATCH net-next] enic: drop IP proto check for vxlan tunnel delete
Date: Fri, 16 Mar 2018 10:50:14 -0400 (EDT) [thread overview]
Message-ID: <20180316.105014.2271384430706235870.davem@redhat.com> (raw)
In-Reply-To: <20180313122433.1185-1-gvaradar@cisco.com>
From: Govindarajulu Varadarajan <gvaradar@cisco.com>
Date: Tue, 13 Mar 2018 05:24:33 -0700
> Commit d11790941dd3 ("enic: Add vxlan offload support for IPv6 pkts")
> added vxlan offload support for IPv6 pkts. Required change in
> enic_udp_tunnel_del was not made. This creates a bug where once user
> adds IPv6 tunnel, hw offload for that cannot be deleted.
>
> This patch removes check for IP proto in tunnel delete path. Driver need
> not check for IP proto since same UDP port cannot be used to create two
> tunnels.
>
> Fixes: d11790941dd3 ("enic: Add vxlan offload support for IPv6 pkts")
> Signed-off-by: Govindarajulu Varadarajan <gvaradar@cisco.com>
Applied, thanks.
prev parent reply other threads:[~2018-03-16 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 12:24 [PATCH net-next] enic: drop IP proto check for vxlan tunnel delete Govindarajulu Varadarajan
2018-03-16 14:50 ` David Miller [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=20180316.105014.2271384430706235870.davem@redhat.com \
--to=davem@redhat.com \
--cc=benve@cisco.com \
--cc=gvaradar@cisco.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