netdev - Re: [RFC] net: refactor multicast/unicast address list

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:	Tue, 16 Jun 2009 13:18:43 +0200
From:	Jiri Pirko <jpirko@...hat.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	Netdev <netdev@...r.kernel.org>
Subject: Re: [RFC] net: refactor multicast/unicast address list

Sat, Jun 13, 2009 at 02:28:14PM CEST, johannes@...solutions.net wrote:
>On Sat, 2009-06-13 at 12:41 +0200, Johannes Berg wrote:
>> I'm trying to use address lists without netdevs, but as
>> a first step I thought it would be good to reduce the
>> amount duplicated code between unicast and multicast
>> lists.
>> 
>> After introducing a new 'struct address_list', we can
>> unify a lot between these. The next step will probably
>> be exporting the __dev_addr_sync and __dev_addr_unsync
>> functions so I can use them without a netdev, but this
>> cleanup can stand on its own.
>
>Sorry, this was based against the wrong tree and now I see that in
>net-next the lists have diverged significantly. Ignore this.

Yes, I've already converted unicast lists to use list_head there. I'm sending
the patch doing the same for multicast lists soon.

Jirka
>
>johannes


--
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