Linux filesystem development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd@bsbernd.com>
To: Amir Goldstein <amir73il@gmail.com>, Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
	fuse-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	Horst Birthelmer <horst@birthelmer.de>
Subject: Re: [PATCH] fuse: add fusex filesystem
Date: Tue, 12 May 2026 15:46:17 +0200	[thread overview]
Message-ID: <89cb66a2-0f38-4b44-8897-50e932ef6153@bsbernd.com> (raw)
In-Reply-To: <CAOQ4uxgoavKU6zNMN9YF5cchvux6CGGxd56BBOJFWX0gkVAChg@mail.gmail.com>



On 5/12/26 15:08, Amir Goldstein wrote:
> On Tue, May 12, 2026 at 10:18 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
>>
>>> I see no reason for fusex to not support lookup by ".", which is
>>> anyway needed for "reconnect", so a fresh FUSEX_NFS_EXPORT opt-in
>>> for "re-export to NFS" may make more sense.
>>
>> Why add reconnect?  If server supports persistent file handles, and
>> all req's get the file handle, then no state (nodeid) needs to be
>> stored by the server.
>>
> 
> Yes, we are saying the same thing.
> What I am saying is that legacy fuse has FUSE_EXPORT_SUPPORT
> which means server supports lookup of "." which libfuse always enabled
> and then we added FUSE_NO_EXPORT_SUPPORT to opt-out of nfs export.
> 
> I am saying that in FUSEX, lookup "." support is implied.
> And that nfs export should always be opt-in (FUSEX_NFS_EXPORT).

I'm confused here, why do we need lookup of "." without NFS export? And
which file system actually supports lookup of "."?
Shouldn't all that be scratched in favor of LOOKUP_HANDLE?

Thanks,
Bernd

  reply	other threads:[~2026-05-12 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 10:20 [PATCH] fuse: add fusex filesystem Miklos Szeredi
2026-05-07  8:31 ` Horst Birthelmer
2026-05-08 13:01   ` Amir Goldstein
2026-05-12  8:17     ` Miklos Szeredi
2026-05-12 13:08       ` Amir Goldstein
2026-05-12 13:46         ` Bernd Schubert [this message]
2026-05-12  8:11   ` Miklos Szeredi
2026-05-12 10:29     ` Horst Birthelmer
2026-05-08 17:29 ` Horst Birthelmer
2026-05-12  8:20   ` Miklos Szeredi
2026-05-11  8:50 ` Horst Birthelmer
2026-05-12  8:34   ` Miklos Szeredi
2026-05-12  5:05 ` Joanne Koong
2026-05-12  9:18   ` Miklos Szeredi
2026-05-12 13:22     ` Amir Goldstein
2026-05-12 19:22       ` Joanne Koong
2026-05-12 17:33     ` Joanne Koong

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=89cb66a2-0f38-4b44-8897-50e932ef6153@bsbernd.com \
    --to=bernd@bsbernd.com \
    --cc=amir73il@gmail.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=horst@birthelmer.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.com \
    /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