Bug#962254: NFS(v4) broken at 4.19.118-2

From	Salvatore Bonaccorso <carnil@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#962254: NFS(v4) broken at 4.19.118-2
Date	2020-06-05 20:40 +0200
Message-ID	<Aepq1-7Uz-1@gated-at.bofh.it> (permalink)
References	(1 earlier) <AeekV-8tp-1@gated-at.bofh.it> <AedoR-7Uq-1@gated-at.bofh.it> <Aep6F-7Oh-3@gated-at.bofh.it> <AedoR-7Uq-1@gated-at.bofh.it> <Aep6F-7Oh-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Hi Elliott,

Thanks for the additional information.

On Fri, Jun 05, 2020 at 10:43:49AM -0700, Elliott Mitchell wrote:
> On Fri, Jun 05, 2020 at 08:44:26AM +0200, Salvatore Bonaccorso wrote:
> > 
> > On Thu, Jun 04, 2020 at 10:16:07PM -0700, Elliott Mitchell wrote:
> > > Somewhere between linux-image-4.19.0-8-amd64/4.19.98+1+deb10u1 and
> > > linux-image-4.19.0-9-amd64/4.19.118+2 NFS, in particular v4 got broken.
> > > Mounting an appropriate filesystem became unreliable, and once mounted
> > > behavior is unpredictable.
> > > 
> > > In particular in the problematic case `umask 022 ; touch foo ; ls -l foo`
> > > yields a -rw-rw-rw- file.
> > > 
> > > This occurs if *both* the server *and* client are on 4.19.118+2.  I have
> > > confirmed this does NOT occur if the server is on a 4.9 kernel.  I have
> > > also confirmed this does NOT occur if the client is on a 4.9 or
> > > 4.19.98+1+deb10u1 kernel.
> > 
> > I cannot reproducde the described behaviour. Can you give more details
> > on your setup?
> > 
> > How do you export the filesystem?
> > What is the underlying filesystem exported?
> > How and whith which options do clients mount the NFS share?
> 
> Presently it is a whole directories being exported to hosts.  The
> filesystem on the server is ZFS.
> 
> Client is mounting hard,intr.  Client is using cachefilesd, but that
> appears unrelated to the issue.
> 
> As this is NFSv4 (v2 and v3 are thoroughly disabled on the server), TCP
> is being used.  The port is non-standard.
> 
> I'm uncertain I properly tried server on 4.9, client on 4.19.118+2 (could
> be this is strictly 4.19.118+2 NFSv4 client code).

This now let some rings bell, the described scenario is very similar
to what was reported in https://bugs.debian.org/934160

Respectively
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 and
https://bugzilla.redhat.com/show_bug.cgi?id=1667761 .

Salvatore

Thread

Bug#962254: NFS(v4) broken at 4.19.118-2 Elliott Mitchell <ehem+debian@m5p.com> - 2020-06-05 07:50 +0200
  Processed: Re: Bug#962254: NFS(v4) broken at 4.19.118-2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-06-05 08:50 +0200
  Bug#962254: NFS(v4) broken at 4.19.118-2 Salvatore Bonaccorso <carnil@debian.org> - 2020-06-05 08:50 +0200
    Bug#962254: NFS(v4) broken at 4.19.118-2 Elliott Mitchell <ehem+debian@m5p.com> - 2020-06-05 20:20 +0200
      Bug#962254: NFS(v4) broken at 4.19.118-2 Salvatore Bonaccorso <carnil@debian.org> - 2020-06-05 20:40 +0200
        Bug#962254: NFS(v4) broken at 4.19.118-2 Elliott Mitchell <ehem+debian@m5p.com> - 2020-06-06 00:40 +0200
        Bug#934160: Bug#962254: NFS(v4) broken at 4.19.118-2 Elliott Mitchell <ehem+debian@m5p.com> - 2020-06-09 04:00 +0200
  Processed: Re: Bug#962254: NFS(v4) broken at 4.19.118-2 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-06-09 04:00 +0200
  Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported ZFS (with acltype=off) (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Salvatore Bonaccorso <carnil@debian.org> - 2020-06-13 15:00 +0200
  Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported ZFS (with acltype=off) (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) "J. Bruce Fields" <bfields@redhat.com> - 2020-06-15 17:10 +0200
    Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Salvatore Bonaccorso <carnil@debian.org> - 2020-06-15 21:00 +0200
  Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) "J. Bruce Fields" <bfields@redhat.com> - 2020-06-16 04:50 +0200
    Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Salvatore Bonaccorso <carnil@debian.org> - 2020-06-16 07:40 +0200
    Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Salvatore Bonaccorso <carnil@debian.org> - 2020-06-16 18:30 +0200
      Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) "J. Bruce Fields" <bfields@redhat.com> - 2020-06-17 03:10 +0200
        Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl Salvatore Bonaccorso <carnil@debian.org> - 2020-06-17 07:10 +0200
  Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Salvatore Bonaccorso <carnil@debian.org> - 2020-06-16 07:40 +0200
  Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) "J. Bruce Fields" <bfields@redhat.com> - 2020-06-17 17:40 +0200
    Bug#962254: Umask ignored when mounting NFSv4.2 share of an exported Filesystem with noacl (was: Re: Bug#962254: NFS(v4) broken at 4.19.118-2) Andreas Gruenbacher <agruenba@redhat.com> - 2020-06-17 19:00 +0200

csiph-web