netdev - Re: [RFC 4/4] net: ppp_generic - introduce net-namespace functionality

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]

Message-ID: <20090111074652.GB7686@localhost>
Date:	Sun, 11 Jan 2009 10:46:52 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	davem@...emloft.net, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, devel@...nvz.org, xemul@...nvz.org
Subject: Re: [RFC 4/4] net: ppp_generic - introduce net-namespace
	functionality

[Paul Mackerras - Sun, Jan 11, 2009 at 11:33:21AM +1100]
| Cyrill Gorcunov writes:
| 
| > From: Cyrill Gorcunov <gorcunov@...il.com>
| > Subecjt: [RFC] net: ppp_generic - introduce net-namespace functionality
| > 
| > - Each namespace contain ppp channels and units separately
| >   with appropriate locks
| 
| This looks like a lot of uglification to me.  Why exactly do
| individual network drivers need to know or care about namespaces?
| 
| Paul.
| 

Unfortunately in the whole series ppp has been change more
then others and it's looks ugly indeed that is why it was RFC.
Namespaces imply isolation of data right? Including private
data being 'user related' -- ie units passed to user in one
namespace should not interfere with units passed to user in
another namespace. So if I will not 'bind' units pool to
namespaces it would be possible to steal unit from one namespace
proposed for another namespace. Right?

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