All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Dan Shelton <dan.f.shelton@gmail.com>
Cc: Tom Talpey <tom@talpey.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Public NFSv4 handle?
Date: Tue, 13 Feb 2024 15:42:31 -0500	[thread overview]
Message-ID: <9fc2587556d2cff9eb1bb61fd210ed5efdf4eba0.camel@kernel.org> (raw)
In-Reply-To: <CAAvCNcAsow-QTPYLm0fUNX3K5X4Aci=aFi+hi4a0S8k19oa-KA@mail.gmail.com>

On Tue, 2024-02-13 at 21:28 +0100, Dan Shelton wrote:
> On Fri, 9 Feb 2024 at 16:32, Jeff Layton <jlayton@kernel.org> wrote:
> > 
> > On Thu, 2024-02-08 at 21:37 -0500, Tom Talpey wrote:
> > > On 2/8/2024 7:19 PM, Dan Shelton wrote:
> > > > ?
> > > > 
> > > > On Thu, 25 Jan 2024 at 02:48, Dan Shelton <dan.f.shelton@gmail.com> wrote:
> > > > > 
> > > > > Hello!
> > > > > 
> > > > > Do the Linux NFSv4 server and client support the NFS public handle?
> > > 
> > > Are you referring the the old WebNFS stuff? That was a v2/v3 thing,
> > > and, I believe, only ever supported by Solaris.
> > > 
> > 
> > One more try! I think my MUA was having issues this morning.
> > 
> > NFSv4.1 supports the PUTPUBFH op:
> > 
> > https://www.rfc-editor.org/rfc/rfc8881.html#name-operation-23-putpubfh-set-p
> > 
> > ...but this op is only for backward compatibility. The Linux server
> > returns the rootfh (as it SHOULD).
> 
> No, I do not consider this "backward compatibility". The "public"
> option is also intended for public servers, like package mirrors (e.g.
> Debian), to have a better solution than http or ftp.
> 
> What does it take to implement a "public" export option?
> 

Just someone with a will to write the patches for it (including a way to
properly test it). I don't have a problem with making the public fh
settable on the Linux server, but we'd need to hear more about how the
client implementation would work.
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2024-02-13 20:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  1:48 Public NFSv4 handle? Dan Shelton
2024-02-09  0:19 ` Dan Shelton
2024-02-09  2:37   ` Tom Talpey
2024-02-09 11:09     ` Jeff Layton
2024-02-09 14:52     ` Jeff Layton
2024-02-09 15:32     ` Jeff Layton
2024-02-13 20:28       ` Dan Shelton
2024-02-13 20:42         ` Jeff Layton [this message]
2024-02-13 20:58         ` Trond Myklebust
2024-02-14  6:12           ` Cedric Blancher
2024-02-15 17:25             ` Frank Filz
2024-02-13 21:16         ` Chuck Lever III

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=9fc2587556d2cff9eb1bb61fd210ed5efdf4eba0.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=dan.f.shelton@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.