From: Al Viro <viro@zeniv.linux.org.uk>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: srvfs: file system for posting open file descriptors into fs namespace
Date: Fri, 7 Aug 2020 17:23:05 +0100 [thread overview]
Message-ID: <20200807162305.GT1236603@ZenIV.linux.org.uk> (raw)
In-Reply-To: <55ef0e9a-fb70-7c4a-e945-4d521180221c@metux.net>
On Fri, Aug 07, 2020 at 01:09:30PM +0200, Enrico Weigelt, metux IT consult wrote:
> Hello folks,
>
>
> here's the first version of my "srvfs" implementation - a synthentic
> filesystem which allows a process to "publish" an open file descriptor
> into the file system, so other processes can continue from there, with
> whatever state the fd is already in.
>
> This is a concept from Plan9. The main purpose is allowing applications
> "dialing" some connection, do initial handshakes (eg. authentication)
> and then publish the connection to other applications, that now can now
> make use of the already dialed connection.
Yeah, but... Linux open() always gets a new struct file instance; how
do you work around that? Some variant of ->atomic_open() API change?
Details, please.
next prev parent reply other threads:[~2020-08-07 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 11:09 srvfs: file system for posting open file descriptors into fs namespace Enrico Weigelt, metux IT consult
2020-08-07 16:23 ` Al Viro [this message]
2020-08-10 11:27 ` Enrico Weigelt, metux IT consult
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=20200807162305.GT1236603@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=info@metux.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).