netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg@fr.ibm.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Daniel Lezcano <dlezcano@fr.ibm.com>,
	Denis Lunev <den@openvz.org>,
	netdev@vger.kernel.org, containers@lists.linux-foundation.org,
	ebiederm@xmission.com, benjamin.thery@bull.net
Subject: Re: [PATCH net-next] [RFC] netns: enable cross-ve Unix sockets
Date: Wed, 01 Oct 2008 15:08:07 +0200	[thread overview]
Message-ID: <48E37637.8080408@fr.ibm.com> (raw)
In-Reply-To: <48E36FDA.5090808@openvz.org>

Pavel Emelyanov wrote:
> Daniel Lezcano wrote:
>> Pavel Emelyanov wrote:
>>>> So there are 2 cases:
>>>>   * full isolation : restriction on VPS
>>>>   * partial isolation : no restriction but *perhaps* problem when migrating
>>>>
>>>> Looks like we need an option per namespace to reduce the isolation for 
>>>> af_unix sockets :)
>>>>   - on (default): current behaviour => full isolation
>>>>   - off : partial isolation
>>> You mean some sysctl, that enables/disables this check in unix_find_socket_byinode?
>> Yes.
> 
> OK. Den, please, do :)

hmm, would that allow sibling namespaces to connect to each other ? If so, 
I'm not in favor of such a solution. 

I understand the need. we had a similar issue with the command line tool 
pgsl. Could we work something out with the capabilities ? or make an 
exception if your ->nsproxy->net_ns == init_net ? 

Thanks,

C.  

  reply	other threads:[~2008-10-01 13:08 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 [this message]
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
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=48E37637.8080408@fr.ibm.com \
    --to=clg@fr.ibm.com \
    --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 \
    --cc=xemul@openvz.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).