netdev - Re: [RFC PATCH] net: Add support for device specific address syncing

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53766D3E.4080904@intel.com>
Date:	Fri, 16 May 2014 12:55:42 -0700
From:	Alexander Duyck <alexander.h.duyck@...el.com>
To:	David Miller <davem@...emloft.net>
CC:	netdev@...r.kernel.org, jeffrey.t.kirsher@...el.com,
	jpirko@...hat.com
Subject: Re: [RFC PATCH] net: Add support for device specific address syncing

On 05/16/2014 12:01 PM, David Miller wrote:
> From: Alexander Duyck <alexander.h.duyck@...el.com>
> Date: Fri, 16 May 2014 11:47:57 -0700
> 
>> I suppose I should break up the loop below though.  It might be better
>> to do all of the usnync operations first before the sync in the case of
>> a interface with a limited number of unicast of multicast filters.
>  ...
>> My primary use case for this is to simplify mailbox operations between
>> two entities such as a PF and VF.  With this the VF only needs to send a
>> request for new addresses instead of having to send the entire list via
>> the mailbox.  The issue most likely to cause an error is a mailbox error
>> which I admit does have some of its own error recovery in the case of a
>> message timeout.
> 
> I definitely agree that we should be doing the unsync()'s first.
> 
> From a quality of implementation standpoint, the promisc mode needs
> should be determined in both sync() and unsync().
> 

I can understand going into promisc on a sync failure, but why would you
do it on an unsync failure, or are you saying that we would be clearing
the flag in unsync?

In general I intended for this to be called in set_rx_mode so if
__dev_uc_sync returns an error indicating insufficient resources we have
to force IFF_PROMISC on because adding a new address failed.  We could
also do the same thing for __dev_mc_sync and IFF_ALLMULTI.

Thanks,

Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html