[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190205152808.2f56d5c0@hermes.lan>
Date: Tue, 5 Feb 2019 15:28:08 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Ido Schimmel <idosch@...lanox.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"dsahern@...il.com" <dsahern@...il.com>,
"ivecera@...hat.com" <ivecera@...hat.com>,
"liali@...hat.com" <liali@...hat.com>, mlxsw <mlxsw@...lanox.com>
Subject: Re: [PATCH iproute2-master] bridge: fdb: Fix FDB dump with strict
checking disabled
On Fri, 25 Jan 2019 17:09:17 +0000
Ido Schimmel <idosch@...lanox.com> wrote:
> While iproute2 correctly uses ifinfomsg struct as the ancillary header
> when requesting an FDB dump on old kernels, it sets the message type to
> RTM_GETLINK. This results in wrong reply being returned.
>
> Fix this by using RTM_GETNEIGH instead.
>
> Before:
> $ bridge fdb show brport dummy0
> Not RTM_NEWNEIGH: 00000158 00000010 00000002
>
> After:
> $ bridge fdb show brport dummy0
> 2a:0b:41:1c:92:d3 vlan 1 master br0 permanent
> 2a:0b:41:1c:92:d3 master br0 permanent
> 33:33:00:00:00:01 self permanent
> 01:00:5e:00:00:01 self permanent
>
> Fixes: 05880354c2cf ("bridge: fdb: Fix filtering with strict checking disabled")
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> Reported-by: LiLiang <liali@...hat.com>
Looks good applied
Powered by blists - more mailing lists