2020-08-29 22:58:58

by Anthony Joseph Messina

[permalink] [raw]
Subject: NFS client cannot "see" files or directories in /home/<username>

I've reported this issue to Fedora:
https://lists.fedoraproject.org/archives/list/[email protected]/
thread/YECR5Q4LLTEQO3RNSXXKOCZUZF53UAST/
https://bugzilla.redhat.com/show_bug.cgi?id=1873720

I've got an NFS client that mounts /home via NFSv4.2 with sec=krb5p. Any
kernel since 5.7.17 through 5.8.4 is unable to "see" files or directories in
the mounted /home/<username> directory with the exception of the first "dot"
directory.

While I cannot see /home/<username>/subdirectory, if I manually cd into /home/
<username>/subdirectory, I can list that subdirectory's contents as normal.

If I mv "/home/<username>/.dotdir" to "/home/<username>/.dotdir.old", I can no
longer see it, and I can see "/home/<username>/.dotnextdir".

If I then mv "/home/<username>/.dotdir.old" back to "/home/
<username>/.dotdir", I am not able to see it and can still only see "/home/
<username>/.dotnextdir"

My last NFS client that can "see" /home/<username> directory contents (normal
operation) is kernel-5.7.15 (I was unable to test 5.7.16)

NFS server upgrades from kernel-5.7.15 through kernel-5.8.4 didn't seem to
have any affect.

I understand this list is for developers, but I'm wondering if any of the NFS
experts can point me in the right direction... Thank you.

--
Anthony - https://messinet.com
F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6


Attachments:
signature.asc (849.00 B)
This is a digitally signed message part.

2020-09-13 17:23:25

by Anthony Joseph Messina

[permalink] [raw]
Subject: Re: NFS client cannot "see" files or directories in /home/<username>

On Saturday, August 29, 2020 5:52:19 PM CDT Anthony Joseph Messina wrote:
> I've reported this issue to Fedora:
> https://lists.fedoraproject.org/archives/list/[email protected]/
> thread/YECR5Q4LLTEQO3RNSXXKOCZUZF53UAST/
> https://bugzilla.redhat.com/show_bug.cgi?id=1873720
>
> I've got an NFS client that mounts /home via NFSv4.2 with sec=krb5p. Any
> kernel since 5.7.17 through 5.8.4 is unable to "see" files or directories in
> the mounted /home/<username> directory with the exception of the first
> "dot" directory.
>
> While I cannot see /home/<username>/subdirectory, if I manually cd into
> /home/ <username>/subdirectory, I can list that subdirectory's contents as
> normal.
>
> If I mv "/home/<username>/.dotdir" to "/home/<username>/.dotdir.old", I can
> no longer see it, and I can see "/home/<username>/.dotnextdir".
>
> If I then mv "/home/<username>/.dotdir.old" back to "/home/
> <username>/.dotdir", I am not able to see it and can still only see "/home/
> <username>/.dotnextdir"
>
> My last NFS client that can "see" /home/<username> directory contents
> (normal operation) is kernel-5.7.15 (I was unable to test 5.7.16)
>
> NFS server upgrades from kernel-5.7.15 through kernel-5.8.4 didn't seem to
> have any affect.
>
> I understand this list is for developers, but I'm wondering if any of the
> NFS experts can point me in the right direction... Thank you.

The Fedora bugzilla provides additional information:

In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c7 a user reports the commit that creates the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b4487b93545214a9db8cbf32e86411677b0cca21

In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c12 another user reports the relationship with exports using the "security_label" option

--
Anthony - https://messinet.com
F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6


Attachments:
signature.asc (849.00 B)
This is a digitally signed message part.

2020-09-19 00:15:30

by Anthony Joseph Messina

[permalink] [raw]
Subject: Re: NFS client cannot "see" files or directories in /home/<username>

On Sunday, September 13, 2020 12:22:25 PM CDT Anthony Joseph Messina wrote:
> On Saturday, August 29, 2020 5:52:19 PM CDT Anthony Joseph Messina wrote:
> > I've reported this issue to Fedora:
> > https://lists.fedoraproject.org/archives/list/[email protected]
> > g/ thread/YECR5Q4LLTEQO3RNSXXKOCZUZF53UAST/
> > https://bugzilla.redhat.com/show_bug.cgi?id=1873720
> >
> > I've got an NFS client that mounts /home via NFSv4.2 with sec=krb5p. Any
> > kernel since 5.7.17 through 5.8.4 is unable to "see" files or directories
> > in the mounted /home/<username> directory with the exception of the first
> > "dot" directory.
> >
> > While I cannot see /home/<username>/subdirectory, if I manually cd into
> > /home/ <username>/subdirectory, I can list that subdirectory's contents as
> > normal.
> >
> > If I mv "/home/<username>/.dotdir" to "/home/<username>/.dotdir.old", I
> > can
> > no longer see it, and I can see "/home/<username>/.dotnextdir".
> >
> > If I then mv "/home/<username>/.dotdir.old" back to "/home/
> > <username>/.dotdir", I am not able to see it and can still only see
> > "/home/
> > <username>/.dotnextdir"
> >
> > My last NFS client that can "see" /home/<username> directory contents
> > (normal operation) is kernel-5.7.15 (I was unable to test 5.7.16)
> >
> > NFS server upgrades from kernel-5.7.15 through kernel-5.8.4 didn't seem to
> > have any affect.
> >
> > I understand this list is for developers, but I'm wondering if any of the
> > NFS experts can point me in the right direction... Thank you.
>
> The Fedora bugzilla provides additional information:
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c7 a user reports the
> commit that creates the issue:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id
> =b4487b93545214a9db8cbf32e86411677b0cca21
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1873720#c12 another user
> reports the relationship with exports using the "security_label" option

This has been resolved with the patch in:
https://marc.info/?l=linux-nfs&m=160020628625265&w=2

--
Anthony - https://messinet.com
F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6


Attachments:
signature.asc (849.00 B)
This is a digitally signed message part.