public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@cs•stanford.edu>
To: Stanislav Kinsbursky <skinsbursky@parallels•com>
Cc: tglx@linutronix•de, mingo@redhat•com, davem@davemloft•net,
	hpa@zytor•com, thierry.reding@avionic-design•de,
	bfields@redhat•com, eric.dumazet@gmail•com, xemul@parallels•com,
	neilb@suse•de, netdev@vger•kernel.org, x86@kernel•org,
	linux-kernel@vger•kernel.org, paul.gortmaker@windriver•com,
	viro@zeniv•linux.org.uk, gorcunov@openvz•org,
	akpm@linux-foundation•org, tim.c.chen@linux•intel.com,
	devel@openvz•org, ebiederm@xmission•com
Subject: Re: [RFC PATCH 0/5] net: socket bind to file descriptor introduced
Date: Wed, 15 Aug 2012 09:52:53 -0700	[thread overview]
Message-ID: <87wr102j2y.fsf@blp.benpfaff.org> (raw)
In-Reply-To: <20120815161141.7598.16682.stgit@localhost.localdomain> (Stanislav Kinsbursky's message of "Wed, 15 Aug 2012 20:21:56 +0400")

Stanislav Kinsbursky <skinsbursky@parallels•com> writes:

> This system call is especially required for UNIX sockets, which has name
> lenght limitation.

The worst of the name length limitations can be worked around by
opening the directory where the socket is to go as a file
descriptor, then using /proc/self/fd/<fd>/<basename> as the name
of the socket.  This technique also works with "connect" and in
other contexts where a struct sockaddr is needed.  At first
glance, it looks like your patches only help with "bind".

  parent reply	other threads:[~2012-08-15 16:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 16:21 [RFC PATCH 0/5] net: socket bind to file descriptor introduced Stanislav Kinsbursky
2012-08-15 16:22 ` [RFC PATCH 1/5] net: cleanup unix_bind() a little Stanislav Kinsbursky
2012-08-15 16:22 ` [RFC PATCH 2/5] net: split unix_bind() Stanislav Kinsbursky
2012-08-15 16:22 ` [RFC PATCH 3/5] net: new protocol operation fbind() introduced Stanislav Kinsbursky
2012-08-15 16:22 ` [RFC PATCH 4/5] net: fbind() for unix sockets protocol operations introduced Stanislav Kinsbursky
2012-08-15 16:22 ` [RFC PATCH 5/5] syscall: sys_fbind() introduced Stanislav Kinsbursky
2012-08-15 16:30   ` H. Peter Anvin
2012-08-15 16:43     ` Stanislav Kinsbursky
2012-08-15 16:52 ` Ben Pfaff [this message]
2012-08-15 17:54   ` [RFC PATCH 0/5] net: socket bind to file descriptor introduced H. Peter Anvin
2012-08-15 19:49 ` Eric W. Biederman
2012-08-15 20:58   ` H. Peter Anvin
2012-08-15 21:25     ` Eric W. Biederman
2012-08-16  3:03 ` Eric W. Biederman
2012-08-16 13:54   ` J. Bruce Fields
2012-08-20 10:18   ` Stanislav Kinsbursky
2012-09-04 19:00     ` J. Bruce Fields
2012-10-05 20:00       ` J. Bruce Fields
2012-10-08  8:37         ` Stanislav Kinsbursky

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=87wr102j2y.fsf@blp.benpfaff.org \
    --to=blp@cs$(echo .)stanford.edu \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=bfields@redhat$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=devel@openvz$(echo .)org \
    --cc=ebiederm@xmission$(echo .)com \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=gorcunov@openvz$(echo .)org \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=mingo@redhat$(echo .)com \
    --cc=neilb@suse$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    --cc=skinsbursky@parallels$(echo .)com \
    --cc=tglx@linutronix$(echo .)de \
    --cc=thierry.reding@avionic-design$(echo .)de \
    --cc=tim.c.chen@linux$(echo .)intel.com \
    --cc=viro@zeniv$(echo .)linux.org.uk \
    --cc=x86@kernel$(echo .)org \
    --cc=xemul@parallels$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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