Re: ls input/output error ("NFS: readdir(/) returns -5") on krb5 NFSv4 client using SHA2

Next message: Ian Rogers: "[PATCH v4 09/10] perf stat: Read tool events last"
Previous message: Ian Rogers: "[PATCH v4 08/10] perf evlist: Reduce affinity use and move into iterator, fix no affinity"
In reply to: Chuck Lever: "Re: ls input/output error (&quot;NFS: readdir(/) returns -5&quot;) on krb5 NFSv4 client using SHA2"
Next in thread: Chuck Lever: "Re: ls input/output error (&quot;NFS: readdir(/) returns -5&quot;) on krb5 NFSv4 client using SHA2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Tyler W. Ross

Date: Thu Nov 13 2025 - 13:06:00 EST

On Thursday, November 13th, 2025 at 10:47 AM, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote:

> > ls-969 [003] ..... 270.327063: rpc_xdr_recvfrom: task:00000008@00000005 head=[0xffff8895c29fef64,140] page=4008(88) tail=[0xffff8895c29feff0,36] len=988
> > ls-969 [003] ..... 270.327067: rpc_xdr_overflow: task:00000008@00000005 nfsv4 READDIR requested=8 p=0xffff8895c29fefec end=0xffff8895c29feff0 xdr=[0xffff8895c29fef64,140]/4008/[0xffff8895c29feff0,36]/988
>
>
> Here's the problem. This is a sign of an XDR decoding issue. If you
> capture the traffic with Wireshark, does Wireshark indicate where the
> XDR is malformed?

Wireshark appears to decode the READDIR reply without issue. Nothing is obviously marked as malformed, and values all appear sane when spot-checking fields in the decoded packet.

TWR