Path: csiph.com!pasdenom.info!weretis.net!feeder8.news.weretis.net!news.nntp4.net!news.hispagatos.org!srl.newsdeef.eu!news.corradoroberto.it!gothmog.csi.it!bofh.it!news.nic.it!robomod From: "Tyler W. Ross" Newsgroups: linux.debian.bugs.dist,linux.kernel,linux.debian.kernel Subject: Bug#1120598: ls input/output error ("NFS: readdir(/) returns -5") on krb5 NFSv4 client using SHA2 Date: Thu, 13 Nov 2025 19:10:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Thu Nov 13 18:07:08 2025 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -2.399 Reply-To: "Tyler W. Ross" , 1120598@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: debian-kernel@lists.debian.org X-Debian-Pr-Message: followup 1120598 X-Debian-Pr-Package: nfs-common X-Debian-Pr-Keywords: upstream moreinfo X-Debian-Pr-Source: nfs-utils Feedback-ID: 101639484:user:proton X-Pm-Message-ID: 1d0c04c3c03391bfbaad55a148ea3741dbfd938d MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Debian-Message: from BTS X-Mailing-List: archive/latest/1936554 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 21 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: "1120598@bugs.debian.org" <1120598@bugs.debian.org>, Jeff Layton , NeilBrown , Scott Mayhew , Steve Dickson , Salvatore Bonaccorso , Olga Kornievskaia , Dai Ngo , Tom Talpey , Trond Myklebust , Anna Schumaker , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org X-Original-Date: Thu, 13 Nov 2025 18:05:36 +0000 X-Original-Message-ID: X-Original-References: <176298368872.955.14091113173156448257.reportbug@nfsclient-sid.ipa.twrlab.net> <8d873978-2df6-4b79-891d-f0fd78485551@oracle.com> <176298368872.955.14091113173156448257.reportbug@nfsclient-sid.ipa.twrlab.net> Xref: csiph.com linux.debian.bugs.dist:1270042 linux.kernel:1743484 linux.debian.kernel:90018 On Thursday, November 13th, 2025 at 10:47 AM, Chuck Lever wrote: > > ls-969 [003] ..... 270.327063: rpc_xdr_recvfrom: task:00000008@00000005= head=3D[0xffff8895c29fef64,140] page=3D4008(88) tail=3D[0xffff8895c29feff0= ,36] len=3D988 > > ls-969 [003] ..... 270.327067: rpc_xdr_overflow: task:00000008@00000005= nfsv4 READDIR requested=3D8 p=3D0xffff8895c29fefec end=3D0xffff8895c29feff= 0 xdr=3D[0xffff8895c29fef64,140]/4008/[0xffff8895c29feff0,36]/988 >=20 >=20 > 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 obv= iously marked as malformed, and values all appear sane when spot-checking f= ields in the decoded packet. TWR