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
| ||
|
Date: Wed, 24 Sep 2014 09:48:11 -0700 From: Cong Wang <cwang@...pensource.com> To: Nicolas Dichtel <nicolas.dichtel@...nd.com> Cc: netdev <netdev@...r.kernel.org>, containers@...ts.linux-foundation.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-api@...r.kernel.org, David Miller <davem@...emloft.net>, "Eric W. Biederman" <ebiederm@...ssion.com>, Stephen Hemminger <stephen@...workplumber.org>, Andrew Morton <akpm@...ux-foundation.org>, Andy Lutomirski <luto@...capital.net> Subject: Re: [RFC PATCH net-next v2 0/5] netns: allow to identify peer netns On Wed, Sep 24, 2014 at 9:31 AM, Nicolas Dichtel <nicolas.dichtel@...nd.com> wrote: >> I think in this case your ID's are still available, but aren't you >> providing a new way >> for the inner netns device to escape which we are trying to avoid? > > It's why the ids depend on user ns. Only if user ns are the same we allow to > get an id for a peer netns. Too late, userns is relatively new, relying on it breaks our existing assumption. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists