From: "J. Bruce Fields" <bfields@fieldses.org>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fill in rqstp->rq_daddr in svc_tcp_recvfrom
Date: Tue, 12 Jul 2005 12:31:46 -0400 [thread overview]
Message-ID: <20050712163146.GC27938@fieldses.org> (raw)
In-Reply-To: <20050712090455.GA9243@suse.de>
On Tue, Jul 12, 2005 at 11:04:56AM +0200, Olaf Kirch wrote:
> Here's a patch we added to SLES in response to a customer bug report:
>
> # Subject: Fill in rqstp->rq_daddr in svc_tcp_recvfrom
> #
> # This patch fills the daddr member of the rpc struct svc_rqst structure for
> # TCP-based sockets in the recvfrom proceedure. Currently, the field is
> # not set thus leaving it with left over garbage from a previous allocation.
> #
> # This makes the behavior consistent between UDP- and TCP-based RPC.
> #
> # This patch enables HA software to failover TCP-based RPC services
> # such as TCP-based NFS.
Could you explain how this patch makes a difference? I can only see the
value of rq_daddr used in one place, in svc_sendto:
if (rqstp->rq_prot == IPPROTO_UDP) {
...
pki->ipi_spec_dst.s_addr = rqstp->rq_daddr;
if (sock_sendmsg(sock, &msg, 0) < 0)
goto out;
}
So it doesn't seem to be used at all in the TCP case. Am I confused?
--b.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-12 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 9:04 [PATCH] Fill in rqstp->rq_daddr in svc_tcp_recvfrom Olaf Kirch
2005-07-12 16:31 ` J. Bruce Fields [this message]
2005-07-13 5:17 ` Olaf Kirch
2005-07-13 14:36 ` Christoph Hellwig
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=20050712163146.GC27938@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.