All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: Use of delayed request information in nlmsvc_lookup_host
Date: Wed, 14 Nov 2007 14:00:25 -0500	[thread overview]
Message-ID: <473B45C9.4060708@oracle.com> (raw)
In-Reply-To: <1195065798.7584.37.camel@heimdal.trondhjem.org>

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

Trond Myklebust wrote:
> On Wed, 2007-11-14 at 13:23 -0500, Chuck Lever wrote:
>> Hi-
>>
>> Historical question here.
>>
>> nlmsvc_lookup_host() has this:
>>
>> struct nlm_host *
>> nlmsvc_lookup_host(struct svc_rqst *rqstp,
>>                          const char *hostname, unsigned int hostname_len)
>> {
>>          struct sockaddr_in ssin = {0};
>>
>>  >>>     ssin.sin_addr = rqstp->rq_daddr.addr;
>>          return nlm_lookup_host(1, svc_addr_in(rqstp),
>>                                 rqstp->rq_prot, rqstp->rq_vers,
>>                                 hostname, hostname_len, &ssin);
>> }
>>
>> Why is it using rq_daddr to construct the lookup target?
>>
>> The problem here is that rq_daddr isn't a full address.  It doesn't have 
>> address family information.  So nlmsvc_lookup_host() just assumes that 
>> what's stored in rq_daddr is always AF_INET.
> 
> Why can't rq_daddr hold address family information? AFAICS there is
> nothing stopping you from setting that in svc_recvfrom() and in
> svc_udp_get_dest_address().

That's correct.  I'm just trying to understand why, historically, 
rq_daddr was just the 32-bit address and not a full sockaddr to begin 
with.  There may be something we're missing, like "we didn't want to add 
another large field to this structure due to memory alignment or 
allocation efficiency concerns".  :-)

> In fact, why isn't rq_daddr defined to be a sockaddr_storage so that it
> can be safely cast into either a sockaddr_in or a sockaddr_in6 after
> checking the ss_family field?

That isn't unreasonable, but see above.

Note also we have the same problem with NLM_REBOOT (see 
nlmsvc_decode_reboot() and nlmsvc_proc_sm_notify()).  These pass and 
store a 32-bit network-endian address rather than constructing a full 
sockaddr.  A similar solution invites itself.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 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
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 314 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-11-14 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 18:23 Use of delayed request information in nlmsvc_lookup_host Chuck Lever
2007-11-14 18:43 ` Trond Myklebust
2007-11-14 19:00   ` Chuck Lever [this message]
2007-11-14 19:32     ` J. Bruce Fields
2007-11-14 19:41     ` Trond Myklebust
2007-11-14 19:50       ` Trond Myklebust
2007-11-14 19:54       ` Chuck Lever
2007-11-15  1:41         ` Neil Brown
2007-11-15 13:55           ` Chuck Lever
2007-11-15 15:54             ` Trond Myklebust
2007-11-15 16:26               ` Chuck Lever
2007-11-15 17:00                 ` Chuck Lever
2007-11-15 17:23               ` Chuck Lever
2007-11-15 17:37                 ` Trond Myklebust
2007-11-15 18:02                   ` Chuck Lever
2007-11-15 16:00             ` Frank van Maarseveen

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=473B45C9.4060708@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.