linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Haiden <scott.b.haiden@gmail.com>
To: trondmy@kernel.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] Fixes for the NFS automounter
Date: Sun, 24 Aug 2025 00:00:32 -0700	[thread overview]
Message-ID: <7a71069c-da16-4c9e-8afa-225211bdea60@gmail.com> (raw)
In-Reply-To: <cover.1754270543.git.trond.myklebust@hammerspace.com>

Hello,

I think this patch 
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b01f21cacde9f2878492cf318fee61bf4ccad323) 
might have broken the getxattr system call over NFS.

On v6.16.1, I was able to call `getxattr` on files in an NFS 4.2 mount, 
but with this patch, running the same command I get:

     $ cd /path/to/nfs4.2/mount
     $ getfattr -n user.hash.sha512 'S01E01 - Kassa.mkv'
     S01E01 - Kassa.mkv: user.hash.sha512: Operation not supported

Without this patch, it just returns the xattr with no problem.

Am I missing a mount option? Or, is it possible this commit introduced a 
bug?

I ran a git bisect between v6.16.1 and v6.16.2 and it pointed to this 
patch's backport to the stable tree.

Thanks,
--Scott


      parent reply	other threads:[~2025-08-24  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04  1:29 [PATCH 0/2] Fixes for the NFS automounter Trond Myklebust
2025-08-04  1:29 ` [PATCH 1/2] NFS: Fix the setting of capabilities when automounting a new filesystem Trond Myklebust
2025-08-04 16:07   ` Benjamin Coddington
2025-08-04  1:29 ` [PATCH 2/2] NFSv4: Remove duplicate lookups, capability probes and fsinfo calls Trond Myklebust
2025-08-04 16:43   ` Benjamin Coddington
2025-08-04 16:54     ` Trond Myklebust
2025-08-04 19:07       ` Benjamin Coddington
2025-08-05 13:35         ` Benjamin Coddington
2025-08-24  7:00 ` Scott Haiden [this message]

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=7a71069c-da16-4c9e-8afa-225211bdea60@gmail.com \
    --to=scott.b.haiden@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).