Re: [PATCH RFC] fuse: add generic file store

From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Peng Tao <bergwolf@gmail.com>
Cc: Alessio Balsini <balsini@android.com>,
	Peng Tao <tao.peng@linux.alibaba.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH RFC] fuse: add generic file store
Date: Tue, 8 Jun 2021 12:49:59 +0200	[thread overview]
Message-ID: <429fc51b-ece0-b5cb-9540-2e7f5b472d73@metux.net> (raw)
In-Reply-To: <CA+a=Yy5moy0Bv=mhsrC9FrY+cEYt8+YJL8TvXQ=N7pNyktccRQ@mail.gmail.com>

On 08.06.21 04:58, Peng Tao wrote:

>> oh, this could be quite what I'm currently intending do implement
>> (just considered 9p instead of fuse as it looks simpler to me):
>>
>> I'd like the server being able to directly send an already opened fd to
>> the client (in response to it calling open()), quite like we can send
>> fd's via unix sockets.
>>
>> The primary use case of that is sending already prepared fd's (eg. an
>> active network connection, locked-down file fd, a device that the client
>> can't open himself, etc).
>>
>> Is that what you're working on ?
> If the server and client run on the same kernel, then yes, the current
> RFC supports your use case as well, E.g.,
> 1. the server opens a file, saves the FD to the kernel, and passes the
> IDR to the client.
> 2. the client retrieves the FD from the kernel
> 
> Does it match your use case?

Seems that's exactly what I'm looking for :)

Could you perhaps give a little example code how it looks in userland ?

--mtx

-- 
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287