From: Pavel Emelyanov <xemul@openvz.org>
To: serge@hallyn.com
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Alexey Dobriyan <adobriyan@openvz.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Fix /proc/net in presence of net namespaces
Date: Fri, 29 Feb 2008 10:44:03 +0300 [thread overview]
Message-ID: <47C7B7C3.4000504@openvz.org> (raw)
In-Reply-To: <20080228211720.GA1232@vino.hallyn.com>
>> Nack. Yet another global set of ids that require us to implement another
>> namespace looks like the wrong way to go.
>
> Sentiment granted, but I'm not sure it can be an issue. It *could* be
> in issue if we moved to a more flexible access control here here any
> netns could access the .netns/N directories for all it's child
> namespaces.
>
> But it can't, and /proc/net is set by the kernel. So the <id> can't be
> an issue for any checkpoint/restart except htat of the whole system, and
> of course on whole-system resume we have no <id> collision worries.
>
> So userspace can't do anything with <id>, so there is no reason to worry
> about it becoming another namespace?
>
> Right?
Right. Thanks, Serge.
> thanks,
> -serge
next prev parent reply other threads:[~2008-02-29 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 15:46 [PATCH 0/2] Fix /proc/net in presence of net namespaces Pavel Emelyanov
2008-02-28 15:49 ` [PATCH 1/2] Add an id to struct net Pavel Emelyanov
2008-02-28 15:51 ` [PATCH 2/2] Make /proc/net a symlink and drop proc shadows Pavel Emelyanov
2008-02-28 19:31 ` [PATCH 0/2] Fix /proc/net in presence of net namespaces Eric W. Biederman
2008-02-28 21:17 ` serge
2008-02-28 22:39 ` Eric W. Biederman
2008-02-29 3:17 ` serge
2008-02-29 8:16 ` Pavel Emelyanov
2008-02-29 15:38 ` serge
2008-02-29 7:58 ` Pavel Emelyanov
2008-03-02 2:03 ` Eric W. Biederman
2008-03-02 2:17 ` Eric W. Biederman
2008-03-03 9:07 ` Pavel Emelyanov
2008-03-04 22:49 ` Eric W. Biederman
2008-03-05 9:43 ` Pavel Emelyanov
2008-02-29 7:44 ` Pavel Emelyanov [this message]
2008-02-29 7:42 ` Pavel Emelyanov
2008-03-02 2:29 ` Eric W. Biederman
2008-03-03 8:52 ` Pavel Emelyanov
2008-03-04 22:23 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47C7B7C3.4000504@openvz.org \
--to=xemul@openvz.org \
--cc=adobriyan@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.