[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0168f8b-8a45-680b-80d8-ed58294774a5@gmail.com>
Date: Tue, 8 Sep 2020 08:34:45 -0600
From: David Ahern <dsahern@...il.com>
To: Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, roopa@...dia.com,
mlxsw@...dia.com, Ido Schimmel <idosch@...dia.com>
Subject: Re: [RFC PATCH net-next 03/22] nexthop: Only emit a notification when
nexthop is actually deleted
On 9/8/20 3:10 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@...dia.com>
>
> Currently, the delete notification is emitted from the error path of
> nexthop_add() and replace_nexthop(), which can be confusing to listeners
> as they are not familiar with the nexthop.
>
> Instead, only emit the notification when the nexthop is actually
> deleted. The following sub-cases are covered:
>
> 1. User space deletes the nexthop
> 2. The nexthop is deleted by the kernel due to a netdev event (e.g.,
> nexthop device going down)
> 3. A group is deleted because its last nexthop is being deleted
> 4. The network namespace of the nexthop device is deleted
>
> Signed-off-by: Ido Schimmel <idosch@...dia.com>
> ---
> net/ipv4/nexthop.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Reviewed-by: David Ahern <dsahern@...il.com>
Powered by blists - more mailing lists