[Bug 283965] nfs: page fault during nfsrpc_readdir

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.