src-test2/lib/libstand/nfs.c, branch stable/6 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F6 2004-01-21T20:12:23Z Clean up error handling in libstand filesystem code to be more consistent: 2004-01-21T20:12:23Z John Baldwin jhb@FreeBSD.org 2004-01-21T20:12:23Z urn:sha1:fb6b710c39b8bbefd730af2d2b8704bd646e0456 - bzipfs and gzipfs now properly return errno values directly from their read routines rather than returning -1. - missing errno values on error returns for the seek routines on almost all filesystems were added. - fstat() now returns -1 if an error occurs rather than ignoring it. - nfs's readdir() routine now reports valid errno values if an error or EOF occurs rather than EPERM (It was just returning 0 for success and 1 for failure). - nullfs used the wrong semantics for every function besides close() and seek(). Getting it right for close() appears to be an accident at that. - read() for buffered files no longer returns 0 (EOF) if an error occurs, but returns -1 instead. Fix a machine check abort caused by the EFI loader trying to open a 2003-03-03T00:58:47Z Marcel Moolenaar marcel@FreeBSD.org 2003-03-03T00:58:47Z urn:sha1:9c73bdcf24bbfedcae8483127ea135ccb39a3155 file in the NFS file system when the underlying device is not a network device. A Sparc64 specific hack for this exact problem was already present (nfs.c:1.9, tftp.c:1.10), but the problem is not specific to Sparc64. The hack has been promoted to a non-i386 test because on non-i386 architectures it's either impossible to have non-network devices coexist in the same loader with the NFS FS, or network and non-network device coexist and NFS filesystems can only be used on top of network devices. I believe i386 pxeboot is where this does not hold. The root cause of this problem is in open.c where each file system is tried until no more file systems exist or a file system returns success. There's no notion of a list of valid file systems given the underlying device and the non-existence of a file can cause the invalid combination to be tried. Stash various networking paramters in the environment for the kernel 2002-07-31T20:17:06Z Jake Burkholder jake@FreeBSD.org 2002-07-31T20:17:06Z urn:sha1:f739b33f57ff17e81e0c9dd401f651738456de49 to pick up, ala pxe. Add a hack (kludge?) to avoid trying to access files backed by disk 2002-07-07T23:01:36Z Jake Burkholder jake@FreeBSD.org 2002-07-07T23:01:36Z urn:sha1:f9751ec2cd2a2c120699dae1eff650c1a56fb861 devices as though they were backed by network devices. Remove 'register' keyword. 2002-03-21T23:39:28Z David E. O'Brien obrien@FreeBSD.org 2002-03-21T23:39:28Z urn:sha1:be04b6d19037a418b377ed2e33c02086cefa2b60 Add __FBSDID()s to libstand 2001-09-30T22:28:01Z Matthew Dillon dillon@FreeBSD.org 2001-09-30T22:28:01Z urn:sha1:e74b6a84ce2dd9e091aabfbaca4d692983662c0d Expose the NFS root node, so that an evil consumer can use it to get the 2000-09-05T22:11:41Z Mike Smith msmith@FreeBSD.org 2000-09-05T22:11:41Z urn:sha1:6910d080a229cf102536b25e5c705535be63c1b2 NFS filehandle for the root mount. Add readdir support to the NFS filesystem in libstand. 2000-05-01T15:03:52Z Paul Saab ps@FreeBSD.org 2000-05-01T15:03:52Z urn:sha1:db667a40a524ed6b14468d2335a8a99c01b65cba Do not attempt to free a nfs node if it is the root node. The root 2000-05-01T10:53:21Z Paul Saab ps@FreeBSD.org 2000-05-01T10:53:21Z urn:sha1:f12d45d9d681163821058c1cbbb1a3d40525bf58 node is statically allocated and is not guarded, so free will panic in nfs_close. Add a readdir function to the loader fsops vector, and implement the 2000-04-29T20:47:10Z Jonathan Lemon jlemon@FreeBSD.org 2000-04-29T20:47:10Z urn:sha1:efb8ff85324712bafcd6a2f12860719f45352762 functionality for some of the filesystesms.