[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170208.143932.1043944264336559559.davem@davemloft.net>
Date: Wed, 08 Feb 2017 14:39:32 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: roopa@...ulusnetworks.com
Cc: netdev@...r.kernel.org, colin.king@...onical.com,
nikolay@...ulusnetworks.com
Subject: Re: [PATCH net-next] bridge: vlan tunnel id info range fill size
calc cleanups
From: Roopa Prabhu <roopa@...ulusnetworks.com>
Date: Tue, 7 Feb 2017 16:12:00 -0800
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> This fixes a bug and cleans up tunnelid range size
> calculation code by using consistent variable names
> and checks in size calculation and fill functions.
>
> tested for a few cases of vlan-vni range mappings:
> (output from patched iproute2):
> $bridge vlan showtunnel
> port vid tunid
> vxlan0 100-105 1000-1005
> 200 2000
> 210 2100
> 211-213 2100-2102
> 214 2104
> 216-217 2108-2109
> 219 2119
>
> Fixes: efa5356b0d97 ("bridge: per vlan dst_metadata netlink support")
> Reported-by: Colin Ian King <colin.king@...onical.com>
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
Applied, thanks Roopa.
Powered by blists - more mailing lists