netdev - Re: [PATCH net-next] openvswitch: set correct protocol on route lookup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALnjE+p9dKTmf=BpjZbM7Yzn58GfgcOQrjKBTsrtjh8LXv8M1A@mail.gmail.com>
Date:	Fri, 5 Dec 2014 09:43:33 -0800
From:	Pravin Shelar <pshelar@...ira.com>
To:	Jiri Benc <jbenc@...hat.com>
Cc:	netdev <netdev@...r.kernel.org>,
	"dev@...nvswitch.org" <dev@...nvswitch.org>,
	Wenyu Zhang <wenyuz@...are.com>
Subject: Re: [PATCH net-next] openvswitch: set correct protocol on route lookup

On Fri, Dec 5, 2014 at 8:24 AM, Jiri Benc <jbenc@...hat.com> wrote:
> Respect what the caller passed to ovs_tunnel_get_egress_info.
>
> Fixes: 8f0aad6f35f7e ("openvswitch: Extend packet attribute for egress tunnel info")
> Signed-off-by: Jiri Benc <jbenc@...hat.com>

Thanks for the fix.
Acked-by: Pravin B Shelar <pshelar@...ira.com>

> ---
>  net/openvswitch/vport.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/openvswitch/vport.c b/net/openvswitch/vport.c
> index e771a46933e5..9584526c0778 100644
> --- a/net/openvswitch/vport.c
> +++ b/net/openvswitch/vport.c
> @@ -600,7 +600,7 @@ int ovs_tunnel_get_egress_info(struct ovs_tunnel_info *egress_tun_info,
>         fl.saddr = tun_key->ipv4_src;
>         fl.flowi4_tos = RT_TOS(tun_key->ipv4_tos);
>         fl.flowi4_mark = skb_mark;
> -       fl.flowi4_proto = IPPROTO_GRE;
> +       fl.flowi4_proto = ipproto;
>
>         rt = ip_route_output_key(net, &fl);
>         if (IS_ERR(rt))
> --
> 1.8.3.1
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html