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  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]
Date:	Tue, 11 Nov 2014 07:38:10 -1000
From:	Scott Feldman <>
To:	Roopa Prabhu <>
Cc:	Jiri Pirko <>, Netdev <>,
	"David S. Miller" <>,,
	Andy Gospodarek <>,
	Thomas Graf <>,,,,,,,,
	"Kirsher, Jeffrey T" <>,, Cong Wang <>,
	"Fastabend, John R" <>,
	Eric Dumazet <>,
	Jamal Hadi Salim <>,
	Florian Fainelli <>,
	John Linville <>,,, Nicolas Dichtel <>,,,
	Aviad Raveh <>,,
	Alexei Starovoitov <>,
	Neil Jerram <>,,,,
	"Ronciak, John" <>,,
	Shrijeet Mukherjee <>,
	Andy Gospodarek <>,
	Benjamin LaHaise <>
Subject: Re: [patch net-next v2 08/10] bridge: add API to notify bridge driver
 of learned FBD on offloaded device

On Tue, Nov 11, 2014 at 4:21 AM, Roopa Prabhu <> wrote:
> On 11/9/14, 2:51 AM, Jiri Pirko wrote:
>> From: Scott Feldman <>
>> When the swdev device learns a new mac/vlan on a port, it sends some async
>> notification to the driver and the driver installs an FDB in the device.
>> To give a holistic system view, the learned mac/vlan should be reflected
>> in the bridge's FBD table, so the user, using normal iproute2 cmds, can
>> view
>> what is currently learned by the device.  This API on the bridge driver
>> gives
>> a way for the swdev driver to install an FBD entry in the bridge FBD
>> table.
>> (And remove one).
>> This is equivalent to the device running these cmds:
>>    bridge fdb [add|del] <mac> dev <dev> vid <vlan id> master
>> This patch needs some extra eyeballs for review, in paricular around the
>> locking and contexts.
> scott/jiri, love that you have handled this case!, This will be useful.
> But, quick question, Cant this also be done using the same ndo_op that is
> done to add the static fdb..?

Maybe.  I think I tried sending netlink msg from swdev driver to
bridge driver, but wasn't able to make it to work.  I'm not sure if
it's possible to do that, in general, send netlink kernel-to-kernel.
The other option is to synthesize a netlink msg with needed attrs and
call ndo in bridge directly.  That feels a little yucky to me.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists