From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Alex Bligh <alex-rWA27mgs/Jz10XsdtD+oqA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Bastian Blank <bastian-yyjItF7Rl6lg9hUCZPvPmw@public.gmane.org>
Subject: Re: CLONE_NEWNET + unix domain sockets
Date: Thu, 28 Apr 2011 13:03:46 -0700 [thread overview]
Message-ID: <m1ei4mdty5.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <E5092261EC5F5ABA2AE6E7EE-F+tRR8lnwRmNj9Bq2fkWzw@public.gmane.org> (Alex Bligh's message of "Mon, 25 Apr 2011 19:54:10 +0100")
Alex Bligh <alex-rWA27mgs/Jz10XsdtD+oqA@public.gmane.org> writes:
> --On 25 April 2011 20:35:00 +0200 Bastian Blank <bastian-yyjItF7Rl6lg9hUCZPvPmw@public.gmane.org>
> wrote:
>
>> On Mon, Apr 25, 2011 at 02:56:25PM +0100, Alex Bligh wrote:
>>> but I don't understand why, or what the semantics are for interaction
>>> between unshare(CLONE_NEWNET) and unix domain sockets. Any ideas?
>>
>> AFAIK sharing unix sockets between network namespaces is supported since
>> 2.6.36 or so.
>
> I'm using 2.6.32-28-generic, and I'm doing
> fork()
> listen()
> unshare(CLONE_NEWNET)
> ...
> accept()
>
> and it seems to be working. Is that forward compatible?
Yes.
Eric
prev parent reply other threads:[~2011-04-28 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 13:56 CLONE_NEWNET + unix domain sockets Alex Bligh
[not found] ` <6E3DBEA16997DE780A11C637-F+tRR8lnwRmNj9Bq2fkWzw@public.gmane.org>
2011-04-25 14:12 ` Serge Hallyn
[not found] ` <20110425141228.GB29132-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2011-04-25 14:43 ` Alex Bligh
2011-04-25 18:35 ` Bastian Blank
[not found] ` <20110425183459.GA29536-0IJIQSrh9RL9UF0aPl6fsj8Kkb2uy4ct@public.gmane.org>
2011-04-25 18:54 ` Alex Bligh
[not found] ` <E5092261EC5F5ABA2AE6E7EE-F+tRR8lnwRmNj9Bq2fkWzw@public.gmane.org>
2011-04-28 20:03 ` Eric W. Biederman [this message]
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=m1ei4mdty5.fsf@fess.ebiederm.org \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=alex-rWA27mgs/Jz10XsdtD+oqA@public.gmane.org \
--cc=bastian-yyjItF7Rl6lg9hUCZPvPmw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 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.