netdev - Re: [PATCH net-next 0/2] Introduce possible_net

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] [day] [month] [year] [list]

Message-Id: <20150312.144015.420979058716247691.davem@davemloft.net>
Date:	Thu, 12 Mar 2015 14:40:15 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org, salo@...gle.com
Subject: Re: [PATCH net-next 0/2] Introduce possible_net_t

From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Wed, 11 Mar 2015 23:03:13 -0500

> The current usage of write_pnet and read_pnet is a little laborious and
> error prone as you only notice if you failed to include them if are
> compiling with network namespaces enabled.
> 
> possible_net_t remedies that by using a type that is 0 bytes when
> network namespaces are disabled and can only be read and written to with
> read_pnet and write_pnet.
> 
> Aka less work and safer for the same effect.
> 
> I kill hold_net and release_net first as are they are haven't been used
> since 2008 and are noise at the points where write_pnet and read_pnet
> are used.
> 
> I have folded in Eric Dumazets suggestions to improve the killing of
> hold_net and release net.  And respon.  I had to respin anyway as
> there was enough changes elsewhere in the tree the previous version
> of these patches did not quite apply cleanly.

Series applied, 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