summaryrefslogtreecommitdiffstats
path: root/sys/rpc
Commit message (Collapse)AuthorAgeFilesLines
* Don't panic because of RPC proto mismatches. Whitespace cleanup.alfred2004-01-171-35/+37
| | | | Submitted by: Jim Rees <rees@umich.edu>
* Prevent a panic when mounting a v2/v3 only server with mount_nfs4.alfred2004-01-131-0/+2
| | | | | Submitted by: Jim Rees <rees@umich.edu> Reported/testing: Florian C. Smeets <flo@kasimir.com>
* Fix a panic when attempting a v4 op against a v3/v2-only server.alfred2004-01-101-10/+12
| | | | | | | It happens because rpcclnt_request is incorrectly returning 0 in the case of an rpc mismatch or auth error. Submitted by: Jim Rees <rees@umich.edu>
* Change the definition of NULL on ia64 (for LP64 compilations) frommarcel2003-12-071-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | an int constant to a long constant. This change improves consistency in the following two ways: 1. The first 8 arguments are always passed in registers on ia64, which by virtue of the generated code implicitly widens ints to longs and allows the use of an 32-bit integral type for 64-bit arguments. Subsequent arguments are passed onto the memory stack, which does not exhibit the same behaviour and consequently do not allow this. In practice this means that variadic functions taking pointers and given NULL (without cast) work as long as the NULL is passed in one of the first 8 arguments. A SIGSEGV is more likely the result if such would be done for stack-based arguments. This is due to the fact that the upper 4 bytes remain undefined. 2. All 64-bit platforms that FreeBSD supports, with the obvious exception of ia64, allow 32-bit integral types (specifically NULL) when 64-bit pointers are expected in variadic functions by way of how the compiler generates code. As such, code that works correctly (whether rightfully so or not) on any platform other than ia64, may fail on ia64. To more easily allow tweaking of the definition of NULL, this commit removes the 12 definitions in the various headers and puts it in a new header that can be included whenever NULL is to be made visible. This commit fixes GNOME, emacs, xemacs and a whole bunch of ports that I don't particularly care about at this time...
* Remove unneeded file. (could be repo removed as nothing ever referenced it.)alfred2003-11-201-101/+0
| | | | Submitted by: Jim Rees <rees@umich.edu>
* Use %zu to printf a size_t instead of an int cast.alfred2003-11-151-3/+3
| | | | Requested by: jmallett, wollman
* Fix compilation warnings on sparc.alfred2003-11-151-2/+2
| | | | Cast sizeof to int for printing with %d.
* University of Michigan's Citi NFSv4 kernel client code.alfred2003-11-144-0/+2675
| | | | Submitted by: Jim Rees <rees@umich.edu>
* Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) andalfred2001-03-191-6/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
* $Id$ -> $FreeBSD$peter1999-08-271-1/+1
|
* Resolve conflicts.wpaul1997-05-281-1/+1
|
* Revert $FreeBSD$ to $Id$peter1997-02-231-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* First commit of a series of cleanups for the libc rpc code which has beenpeter1996-12-301-7/+3
| | | | | | | | | | | suffering a bad case neglect for the last few years. - Add full prototypes, including to function pointers. - Make the wire protocols 64-bit type safe, eg: 32 bit quantities are int32_t, not long. The orginal rpc code was implemented when an int could be 16 bits. Obtained from: a diff of FreeBSD vs. OpenBSD/NetBSD rpc code.
* Fix a bunch of spelling errors in the comment fieldsmpp1996-01-301-2/+2
| | | | of a bunch of system include files.
* Remove trailing whitespace.rgrimes1995-05-301-6/+6
|
* Use the header files that are compatible with the code just moved overwollman1994-08-071-13/+16
| | | | from 1.1.5.
* Install RPC headers from include, like they always should have been.wollman1994-08-041-0/+63
OpenPOWER on IntegriCloud