diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2009-03-18 20:47:14 -0400 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2009-03-28 15:56:04 -0400 |
| commit | 126e4bc3b3b446482696377f67a634c76eaf2e9c (patch) | |
| tree | baa96bad06505f212e59b7e1fa557658412979c8 /fs/eventfd.c | |
| parent | 3aba45536fe8f92aa07bcdfd2fb1cf17eec7d786 (diff) | |
| download | linux-126e4bc3b3b446482696377f67a634c76eaf2e9c.tar.gz linux-126e4bc3b3b446482696377f67a634c76eaf2e9c.tar.bz2 linux-126e4bc3b3b446482696377f67a634c76eaf2e9c.zip | |
SUNRPC: rpcbind actually interprets r_owner string
RFC 1833 has little to say about the contents of r_owner; it only
specifies that it is a string, and states that it is used to control
who can UNSET an entry.
Our port of rpcbind (from Sun) assumes this string contains a numeric
UID value, not alphabetical or symbolic characters, but checks this
value only for AF_LOCAL RPCB_SET or RPCB_UNSET requests. In all other
cases, rpcbind ignores the contents of the r_owner string.
The reference user space implementation of rpcb_set(3) uses a numeric
UID for all SET/UNSET requests (even via the network) and an empty
string for all other requests. We emulate that behavior here to
maintain bug-for-bug compatibility.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs/eventfd.c')
0 files changed, 0 insertions, 0 deletions