From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: <linux-fsdevel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: <cgroups@vger.kernel.org>,
<containers@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
"bfields@fieldses.org" <bfields@fieldses.org>,
James Bottomley <jbottomley@parallels.com>,
"devel@openvz.org" <devel@openvz.org>
Subject: [RFC] connectat() and bindat() system calls
Date: Wed, 6 Jun 2012 12:38:51 +0400 [thread overview]
Message-ID: <4FCF171B.8000207@parallels.com> (raw)
Hello.
I'd really appreciate for any comments on subj - implementation of new system
call: connectat and bindat.
Reasons for new system calls:
1) Path length for UNIX sockets is limited to 108 symbols.
Syscalls are useful as is since removes limitation.
2) Ability to perform connect/bind calls to UNIX sockets starting from specified
path in kernel.
This is required for proper support of kernel connect operations in SUNRPC
layer. Which, in turn, required for proper support of NFS in containers.
These system calls could be used only for non-abstract UNIX sockets, obviously.
Possible implementation could be adding of struct path pointer to sockaddr_un.
But this pointer have to valid only for connect and bind calls, and caller have
to hold and release path by himself.
--
Best regards,
Stanislav Kinsbursky
reply other threads:[~2012-06-06 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FCF171B.8000207@parallels.com \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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).