linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org,
	Subrata Modak
	<subrata-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: Re: [patch 1/2][RFC] add socketat syscall
Date: Fri, 07 Nov 2008 13:19:47 +0100	[thread overview]
Message-ID: <49143263.1040604@fr.ibm.com> (raw)
In-Reply-To: <491318DC.4000300-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>

Daniel Lezcano wrote:
> Michael Kerrisk wrote:
>>> On Fri, Oct 31, 2008 at 4:56 PM, Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org> wrote:
>>>> This patch adds the socketat syscall which allows to specify in
>>>> which network namespace we want to create a socket. The network
>>>> namespace destination is referred by a socket fd previously opened
>>>> in the destination network namespace.
>> Daniel,
>>
>> Is there any documentation for this system call, and/or test programs?
> 
> Not yet.
> 
> This small patch is a proposition to Andreas and Vivien to have a single 
> process being able to manage several network namespaces.
> 
> When a process unshares the network, it creates a socket which is used 
> as a socket control (it belongs to the network namespace). Each time a 
> network namespace is created, a socket control is created.
> 
> When the process has to create a socket for a specific network 
> namespace, it can use the socket control to specify it. This is the 
> purpose of the socketat syscall.

what about eric's proposal of adding an fd argument to sys_socket() ? was it 
dropped ?

C. 

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

  parent reply	other threads:[~2008-11-07 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081031215602.655672481@fr.ibm.com>
     [not found] ` <20081031215900.810348746@fr.ibm.com>
     [not found]   ` <20081031215900.810348746-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-06 13:22     ` [patch 1/2][RFC] add socketat syscall Michael Kerrisk
     [not found]       ` <517f3f820811060522i7b3518aen47907a34b38adee9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-06 13:27         ` Daniel Lezcano
2008-11-06 15:46         ` Michael Kerrisk
     [not found]           ` <cfd18e0f0811060746l77fbe6fel83402ba543fccb38-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-06 16:18             ` Daniel Lezcano
     [not found]               ` <491318DC.4000300-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-07  9:45                 ` Subrata Modak
2008-11-07 12:19                 ` Cedric Le Goater [this message]
     [not found]                   ` <49143263.1040604-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-07 12:33                     ` Daniel Lezcano
     [not found]                       ` <49143594.8030109-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-11-07 16:09                         ` Eric W. Biederman
2008-11-12 10:33                         ` Vivien Chappelier
     [not found]                           ` <491AB112.1030806-L+G57L1VLRbR7s880joybQ@public.gmane.org>
2008-11-12 15:24                             ` Eric W. Biederman
     [not found]                               ` <m1vdutotky.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-11-12 15:59                                 ` Vivien Chappelier

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=49143263.1040604@fr.ibm.com \
    --to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=subrata-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 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).