public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Scott Mayhew <smayhew@redhat.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [nfs-utils PATCH] exports: Fix referrals when --enable-junction=no
Date: Tue, 3 Dec 2024 14:28:47 +0000	[thread overview]
Message-ID: <A47A9D21-EF59-4263-AC63-059FB0661CA8@oracle.com> (raw)
In-Reply-To: <6b8990cc-ec29-4e01-acd6-8c7ec6487d99@redhat.com>



> On Dec 2, 2024, at 10:19 PM, Steve Dickson <SteveD@redhat.com> wrote:
> 
> Hey,
> 
> On 12/2/24 3:30 PM, Scott Mayhew wrote:
>> Commit 15dc0bea ("exportd: Moved cache upcalls routines into
>> libexport.a") caused write_fsloc() to be elided when junction support is
>> disabled.  Get rid of the bogus #ifdef HAVE_JUNCTION_SUPPORT blocks so
>> that referrals work again (the only #ifdef HAVE_JUNCTION_SUPPORT should
>> be around actual junction code).
> Why not just take the enable_junction config variable
> out of configure.ac as well?

It's not generally good practice, but I will break up your
sentence below to reply to each bit. There is something to
unpack in each part.


> If we want junctions/referrals (which are the same)
> IMHO...

Junctions and refer= are related, but they aren't
the same. As Scott demonstrated, a junction is a file
system object that stores NFSv4 referral information.
The "refer=" export option stores that information in
/etc/exports.

The common part of these two mechanisms resides in
NFSD, which turns that information into the response
to a GETATTR(fs_locations).


> on all the time...

We want "refer=" on all the time, yes.

Junction support has to be enabled manually. This is
because it depends on libxml2, which not every distro
wants to, or can, pull into its nfs-utils package.

That is in fact exactly how Salvatore is using this
option. The stable version of Debian's nfs-utils
package does not want libxml2, so junction support is
disabled there. But they /do/ want "refer=" support.


> Lets not be able to turn them off at all?

That would be nice, but it's not yet practical for
every distro to enable it.

I am told that Debian unstable's nfs-utils will
enable junction support, and has added the libxml2
dependency successfully.

We will get there eventually.


> Point being... if we are going remove 3 of the 4
> HAVE_JUNCTION_SUPPORT ifdefs... let get ride of
> all of them.


--
Chuck Lever



  parent reply	other threads:[~2024-12-03 14:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 16:58 NFSv4 referrals broken when not enabling junction support Salvatore Bonaccorso
2024-10-08 10:12 ` Steve Dickson
2024-10-20 14:37   ` Salvatore Bonaccorso
2024-10-25 20:14     ` Salvatore Bonaccorso
2024-10-26 13:04       ` Steve Dickson
2024-10-26 15:56         ` Salvatore Bonaccorso
2024-11-26  4:57         ` Salvatore Bonaccorso
2024-12-02 18:26           ` Steve Dickson
2024-12-02 19:46             ` Salvatore Bonaccorso
2024-12-02 19:57               ` Steve Dickson
2024-12-02 20:02                 ` Chuck Lever III
2024-12-03 12:04                   ` Steve Dickson
2024-12-02 20:22                 ` Salvatore Bonaccorso
2024-12-02 20:30                 ` [nfs-utils PATCH] exports: Fix referrals when --enable-junction=no Scott Mayhew
2024-12-02 21:25                   ` Roland Mainz
2024-12-02 21:41                   ` Chuck Lever
2024-12-03 12:11                     ` Steve Dickson
2024-12-03  3:19                   ` Steve Dickson
2024-12-03 12:43                     ` Scott Mayhew
2024-12-03 14:25                       ` Steve Dickson
2024-12-03 14:28                     ` Chuck Lever III [this message]
2024-12-03 16:02                       ` Steve Dickson
2024-12-03 16:12                         ` Chuck Lever III
2024-12-09 10:26                   ` Steve Dickson
2024-12-02 20:00               ` NFSv4 referrals broken when not enabling junction support 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=A47A9D21-EF59-4263-AC63-059FB0661CA8@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smayhew@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