Home
last modified time | relevance | path

Searched hist:"82 c0aec8de23f4429fb7af67e2499152530e12f5" (Results 1 – 1 of 1) sorted by relevance

/freebsd/sys/fs/cd9660/
H A Dcd9660_vnops.cdiff 82c0aec8de23f4429fb7af67e2499152530e12f5 Sun Sep 05 13:18:53 CEST 2004 Tim J. Robbins <tjr@FreeBSD.org> Temporarily back out revision 1.77. This changed cd9660_getattr() and
cd9660_readdir() to return the address of the file's first data block as
the inode number instead of the address of the directory entry, but
neglected to update cd9660_vget_internal() for the new inode numbering
scheme.

Since the NFS server calls VFS_VGET (cd9660_vget()) with inode numbers
returned through VOP_READDIR (cd9660_readdir()) when servicing a READDIRPLUS
request, these two interfaces must agree on the numbering scheme; failure to
do so caused panics and/or bogus information about the entries to be returned
to clients using READDIRPLUS (Solaris, FreeBSD w/ mount -o rdirplus).

PR: 63446
diff 82c0aec8de23f4429fb7af67e2499152530e12f5 Sun Sep 05 13:18:53 CEST 2004 Tim J. Robbins <tjr@FreeBSD.org> Temporarily back out revision 1.77. This changed cd9660_getattr() and
cd9660_readdir() to return the address of the file's first data block as
the inode number instead of the address of the directory entry, but
neglected to update cd9660_vget_internal() for the new inode numbering
scheme.

Since the NFS server calls VFS_VGET (cd9660_vget()) with inode numbers
returned through VOP_READDIR (cd9660_readdir()) when servicing a READDIRPLUS
request, these two interfaces must agree on the numbering scheme; failure to
do so caused panics and/or bogus information about the entries to be returned
to clients using READDIRPLUS (Solaris, FreeBSD w/ mount -o rdirplus).

PR: 63446