netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
	netdev@vger.kernel.org, containers@lists.linux-foundation.org,
	benjamin.thery@bull.net, ebiederm@xmission.com
Subject: Re: [PATCH net-next] [RFC] netns: enable cross-ve Unix sockets
Date: Wed, 01 Oct 2008 19:42:50 +0400	[thread overview]
Message-ID: <48E39A7A.8090800@openvz.org> (raw)
In-Reply-To: <48E3998D.4040709@fr.ibm.com>

Daniel Lezcano wrote:
> Pavel Emelyanov wrote:
>>> Yes per namespace, I agree.
>>>
>>> If the option is controlled by the parent and it is done by sysctl, you 
>>> will have to make proc/sys per namespace like Pavel did with /proc/net, no ?
>> /proc/sys is already per namespace actually ;) Or what did you mean by that?
> 
> 
> Effectively I was not clear :)
> 
> I meant, you can not access /proc/sys from outside the namespace like 
> /proc/net which can be followed up by /proc/<pid>/net outside the namespace.

Ah! I've got it. Well, I think after Al Viro finishes with sysctl
rework this possibility will appear, but Denis actually persuaded me
in his POV - if we do want to disable shared sockets we *can* do this
by putting containers in proper mount namespaces of chroot environments.

> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2008-10-01 15:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 10:54 [PATCH net-next] [RFC] netns: enable cross-ve Unix sockets Denis V. Lunev
2008-10-01 11:13 ` Daniel Lezcano
2008-10-01 11:32   ` Denis V. Lunev
2008-10-01 11:55     ` Daniel Lezcano
     [not found]       ` <48E3653C.1070701-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-10-01 12:03         ` Denis V. Lunev
2008-10-01 12:19           ` Daniel Lezcano
2008-10-01 12:24             ` Pavel Emelyanov
2008-10-01 12:31               ` Daniel Lezcano
2008-10-01 12:40                 ` Pavel Emelyanov
2008-10-01 13:08                   ` Cedric Le Goater
2008-10-01 13:50                     ` Daniel Lezcano
2008-10-01 15:07                       ` Cedric Le Goater
2008-10-01 13:11                 ` Denis V. Lunev
2008-10-01 13:46                   ` Daniel Lezcano
2008-10-01 14:54                     ` Denis V. Lunev
2008-10-01 15:18                       ` Daniel Lezcano
2008-10-01 15:31                         ` Pavel Emelyanov
2008-10-01 15:38                           ` Daniel Lezcano
2008-10-01 15:42                             ` Pavel Emelyanov [this message]
2008-10-01 16:15                               ` Daniel Lezcano
2008-10-02 10:21                                 ` Denis V. Lunev
2008-10-02 20:03                                   ` 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=48E39A7A.8090800@openvz.org \
    --to=xemul@openvz.org \
    --cc=benjamin.thery@bull.net \
    --cc=containers@lists.linux-foundation.org \
    --cc=den@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).