Re: NFS 4.2 "RPC struct is bad" revisited (with much more detail)

From: J David <j.david.lists_at_gmail.com>
Date: Mon, 02 Dec 2024 20:23:08 UTC 
On Sun, Dec 1, 2024 at 8:03 PM Rick Macklem <rick.macklem@gmail.com> wrote:
> Well, this indicates the Debian server is broken. A bitmap and associated
> attribute values are required for a GETATTR reply of NFS4_OK.
> This clearly says they are not there.
>
> That would result in the client saying the RPC is bad.

Even if the response to that isn't "A problem that occurs only with
FreeBSD clients is a FreeBSD client problem; it shouldn't do the thing
that causes that to happen," it could take quite some time for any
change made by the linux-nfs crowd to filter through to reaching a
production Debian release.

Is there a reasonable way to apply Postel's law here and modify the
client to warn on but accept this behavior rather than erroring out in
a way that renders the file structure unusable indefinitely?

Even refusing to cache this response if it is unusable would probably
be an improvement.

Thanks!