diff options
author | Chuck Lever <chuck.lever@oracle.com> | 2009-03-18 20:45:28 -0400 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2009-03-28 15:52:08 -0400 |
commit | 776bd5c7a207de546918f805090bfc823d2660c8 (patch) | |
tree | bf99838d1e073b8caee80bd79027d69892585d5c /crypto | |
parent | 7fe5c398fc2186ed586db11106a6692d871d0d58 (diff) | |
download | talos-op-linux-776bd5c7a207de546918f805090bfc823d2660c8.tar.gz talos-op-linux-776bd5c7a207de546918f805090bfc823d2660c8.zip |
SUNRPC: Don't flag empty RPCB_GETADDR reply as bogus
In 2007, commit e65fe3976f594603ed7b1b4a99d3e9b867f573ea added
additional sanity checking to rpcb_decode_getaddr() to make sure we
were getting a reply that was long enough to be an actual universal
address. If the uaddr string isn't long enough, the XDR decoder
returns EIO.
However, an empty string is a valid RPCB_GETADDR response if the
requested service isn't registered. Moreover, "::.n.m" is also a
valid RPCB_GETADDR response for IPv6 addresses that is shorter
than rpcb_decode_getaddr()'s lower limit of 11. So this sanity
check introduced a regression for rpcbind requests against IPv6
remotes.
So revert the lower bound check added by commit
e65fe3976f594603ed7b1b4a99d3e9b867f573ea, and add an explicit check
for an empty uaddr string, similar to libtirpc's rpcb_getaddr(3).
Pointed-out-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions