All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@Oracle.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Linux rpcbind daemon doesn't work with v4 GETVERSADDR requests
Date: Thu, 16 Aug 2007 16:31:25 -0400	[thread overview]
Message-ID: <46C4B41D.6010406@oracle.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 385 bytes --]

Hi Steve-

I was testing the in-kernel rpcbind client to fix a bug with the 
GETVERSADDR request... and noticed that the Linux rpcbind client doesn't 
respond correctly to these requests.  I get a 4-byte zero response 
instead of the expected 24-byte universal address.

I finished my testing against a Solaris Nevada snv_63 server.  You could 
use something like that as a reference.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-08-16 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 20:31 Chuck Lever [this message]
2007-08-17 10:54 ` Linux rpcbind daemon doesn't work with v4 GETVERSADDR requests Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46C4B41D.6010406@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.