netdev - Re: [net-next PATCH 0/2] Provide common means for device address sync

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 01 Jun 2014 22:04:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alexander.h.duyck@...el.com
Cc:	ssujith@...co.com, neepatel@...co.com, _govind@....com,
	benve@...co.com, netdev@...r.kernel.org,
	jeffrey.t.kirsher@...el.com
Subject: Re: [net-next PATCH 0/2] Provide common means for device address
 sync

From: Alexander Duyck <alexander.h.duyck@...el.com>
Date: Wed, 28 May 2014 18:44:41 -0700

> The following series implements a means for synchronizing both unicast and
> multicast addresses on a device interface.  The code is based on the original
> implementation of dev_uc_sync that was available for syncing a VLAN to the
> lower dev.
> 
> The original reason for coming up for this patch is a driver that is still in
> the early stages of development.  The nearest driver I could find that
> appeared to have the same limitations as the driver I was working on was the
> Cisco enic driver.  For this reason I chose it as the first driver to make use
> of this interface publicly.
> 
> However, I do not have a Cisco enic interface so I have only been able to
> compile test any changes made to the driver.  I tried to keep this change as
> simple as possible to avoid any issues.  Any help with testing would be
> greatly appreciated.

I'll apply this series once there is some testing feedback, thanks.
--
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