[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe209498b9241ad879f056923a86a38f95cd390e.camel@kernel.org>
Date: Tue, 03 Dec 2024 06:32:20 -0800
From: Jeff Layton <jlayton@...nel.org>
To: Christian Brauner <brauner@...nel.org>, Chuck Lever III
<chuck.lever@...cle.com>
Cc: Amir Goldstein <amir73il@...il.com>, Erin Shepherd
<erin.shepherd@....eu>, Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux NFS
Mailing List <linux-nfs@...r.kernel.org>, stable <stable@...nel.org>,
Wedson Almeida Filho <wedsonaf@...il.com>
Subject: Re: [PATCH 0/4] exportfs: add flag to allow marking export
operations as only supporting file handles
On Tue, 2024-12-03 at 10:08 +0100, Christian Brauner wrote:
> > Though, I wonder if a similar but separate prohibition
> > mechanism might be necessary for other in-kernel network
> > file system server implementations (eg, ksmbd).
>
> Oh hm, interesting question.
> I have no idea how ksmbd or 9p "exports" work. I really hope they don't
> allow exporting arbitrary pseudo-fses.
SMB is path-based so there's no worry about filehandles there. It looks
like ksmbd keeps a set of ksmbd_share_config objects, that are
configured by userland. If someone deliberately shares stuff under
/proc, then I guess they get to keep all of the pieces. ;)
9P does use filehandles, but there is no in-kernel server, so far.
Wedson had one in development at one point [1], but I haven't heard
anything about it in a while.
[1]: https://kangrejos.com/Async%20Rust%20and%209p%20server.pdf
--
Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists