Date: Thu, 09 Jan 2025 20:53:20 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283965] nfs: page fault during nfsrpc_readdir Message-ID: <bug-283965-227-248VaNBvKT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283965-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283965 --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- I've determined that the cause of the failure in nfscl_invalidfname is because my test fuse file system includes the NUL character in its readdir entries. That is, it replies something like this: ents[0].d_namlen = 3; ents[0].d_name = ".."; ents[1].d_namlen = 2; ents[1].d_name = "."; I can and will fix that in the tests. But I can't guarantee that other fuse file systems won't do the same. Even if I have fusefs sanitize these strings in-kernel, other file systems might do the same. For example, I see that ext2 trusts the on-disk data, and copies it into a dirent without sanitizing it. So NFS must be able to handle that. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283965-227-248VaNBvKT>