[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170110.204741.1506942846730150633.davem@davemloft.net>
Date: Tue, 10 Jan 2017 20:47:41 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: mahesh@...dewar.net
Cc: netdev@...r.kernel.org, maheshb@...gle.com, edumazet@...gle.com,
davem@...emloft.org
Subject: Re: [PATCH next v2] ipvlan: improvise dev_id generation logic in
IPvlan
From: Mahesh Bandewar <mahesh@...dewar.net>
Date: Mon, 9 Jan 2017 15:05:54 -0800
> From: Mahesh Bandewar <maheshb@...gle.com>
>
> The patch 009146d117b ("ipvlan: assign unique dev-id for each slave
> device.") used ida_simple_get() to generate dev_ids assigned to the
> slave devices. However (Eric has pointed out that) there is a shortcoming
> with that approach as it always uses the first available ID. This
> becomes a problem when a slave gets deleted and a new slave gets added.
> The ID gets reassigned causing the new slave to get the same link-local
> address. This side-effect is undesirable.
>
> This patch adds a per-port variable that keeps track of the IDs
> assigned and used as the stat-base for the IDR api. This base will be
> wrapped around when it reaches the MAX (0xFFFE) value possibly on a
> busy system where slaves are added and deleted routinely.
>
> Fixes: 009146d117b ("ipvlan: assign unique dev-id for each slave device.")
> Signed-off-by: Mahesh Bandewar <maheshb@...gle.com>
> CC: Eric Dumazet <edumazet@...gle.com>
> CC: David Miller <davem@...emloft.org>
> ---
> v1 -> v2
> Implemented Dave's comments and reinstated IDR API.
Applied, thanks.
Powered by blists - more mailing lists