From: Steve Dickson <SteveD@redhat.com>
To: "Steinar H. Gunderson"
<sgunderson-jG/AHqQBv7lBDgjK7y7TUQ@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] AF_INET6 support for probe_bothports()
Date: Mon, 08 Dec 2008 14:26:32 -0500 [thread overview]
Message-ID: <493D74E8.8050908@RedHat.com> (raw)
In-Reply-To: <20081208150219.GB12390-6Z/AllhyZU4@public.gmane.org>
Steinar H. Gunderson wrote:
> On Mon, Dec 08, 2008 at 08:46:36AM -0500, Steve Dickson wrote:
>> typedef struct {
>> char **hostname;
>> struct sockaddr_in saddr;
>> struct pmap pmap;
>> } clnt_addr_t;
>>
>> Why isn't saddr a struct sockaddr instead of a struct sockaddr_in?
>>
>> It seems at the beginning of each routine saddr is always being
>> typecast into a struct sockaddr pointer.... So wouldn't be easier
>> and cleaner to simply make sadd a struct sockaddr or am I missing
>> something?
>
> I'm sure most people here know this, but still, be careful: If you ever
> intend to store an IPv6 address somewhere, the field in the struct should be
> a sockaddr_storage. sockaddr (or sockaddr_in, for that matter) is not big
> enough to store a sockaddr_in6.
Understood... But isn't a struct sockaddr large enough to store
a IPv6 address? Its no biggie... but what caught my eye was usually
struct sockaddr are typecast into sockaddr_in, not the other away around.
steved.
next prev parent reply other threads:[~2008-12-08 19:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 17:59 [PATCH 0/3] AF_INET6 support for probe_bothports() Chuck Lever
[not found] ` <20081202175403.5206.91389.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-12-02 17:59 ` [PATCH 1/3] mount command: full support for AF_INET6 addresses in probe_port() Chuck Lever
2008-12-02 17:59 ` [PATCH 2/3] mount command: support AF_INET6 in probe_nfsport() and probe_mntport() Chuck Lever
2008-12-02 18:00 ` [PATCH 3/3] mount command: AF_INET6 support for probe_bothports() Chuck Lever
2008-12-08 13:46 ` [PATCH 0/3] " Steve Dickson
[not found] ` <493D253C.2040809-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-08 15:02 ` Steinar H. Gunderson
[not found] ` <20081208150219.GB12390-6Z/AllhyZU4@public.gmane.org>
2008-12-08 19:26 ` Steve Dickson [this message]
[not found] ` <493D74E8.8050908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-08 19:31 ` Chuck Lever
2008-12-08 18:48 ` Chuck Lever
2008-12-08 22:55 ` Steve Dickson
[not found] ` <493DA5EC.5090805-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-08 23:28 ` Steinar H. Gunderson
[not found] ` <20081208232816.GA18856-6Z/AllhyZU4@public.gmane.org>
2008-12-08 23:38 ` Chuck Lever
2008-12-09 19:17 ` Steve Dickson
[not found] ` <493EC42C.2080901-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-09 20:31 ` Trond Myklebust
2008-12-08 23:34 ` Chuck Lever
2008-12-11 16:06 ` 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=493D74E8.8050908@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sgunderson-jG/AHqQBv7lBDgjK7y7TUQ@public.gmane.org \
/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.