From: Cong Wang <amwang@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next 0/7] net: introduce generic type and helpers for IP address
Date: Tue, 23 Jul 2013 10:26:37 +0800 [thread overview]
Message-ID: <1374546397.24933.10.camel@cr0> (raw)
In-Reply-To: <1374545774.8308.5.camel@joe-AO722>
On Mon, 2013-07-22 at 19:16 -0700, Joe Perches wrote:
> On Tue, 2013-07-23 at 10:00 +0800, Cong Wang wrote:
> > On Mon, 2013-07-22 at 13:44 -0700, Joe Perches wrote:
> > >
> > > I see no reason why vsprint's support for
> > > "struct sockaddr *" %pIS should be removed.
> > >
> > > %pIS and %pIA can both exist.
>
> > Because there is no need to keep both of them, struct sockaddr can be
> > safely converted to union inet_addr.
>
> That's a bit fragile.
> The cost of keeping %pIS is pretty low.
I knew, but again, there is no need at all.
>
> Also, if there is ever a check for %p<type>,
> then using:
>
> struct sockaddr *foo = bar;
> ...
> snprintf(buf, len, "%pIA", foo)
>
> would need foo to be cast first to union inet_addr *
>
> snprintf(buf, len, "%pIA", (union inet_addr *)foo);
>
>
You don't have to, compiler doesn't check the new specifier, and it is
safe even without any casting.
What's more, the existing %pIS user (sctp) is already converted to union
inet_addr, see patch 6/7.
next prev parent reply other threads:[~2013-07-23 2:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:05 [Patch net-next 0/7] net: introduce generic type and helpers for IP address Cong Wang
2013-07-22 7:05 ` [Patch net-next 1/7] net: introduce generic union inet_addr Cong Wang
2013-07-22 7:05 ` [Patch net-next 2/7] net: introduce generic simple_inet_pton() Cong Wang
2013-07-22 7:05 ` [Patch net-next 3/7] inetpeer: use generic union inet_addr Cong Wang
2013-07-22 15:18 ` Eric Dumazet
2013-07-23 2:05 ` Cong Wang
2013-07-23 2:26 ` Eric Dumazet
2013-07-23 3:38 ` Cong Wang
2013-07-22 7:05 ` [Patch net-next 4/7] sunrpc: " Cong Wang
2013-07-23 16:40 ` J. Bruce Fields
2013-07-23 16:40 ` J. Bruce Fields
2013-07-25 12:34 ` Cong Wang
2013-07-25 12:34 ` Cong Wang
2013-07-25 12:54 ` J. Bruce Fields
2013-07-22 7:05 ` [Cluster-devel] [Patch net-next 5/7] fs: use generic union inet_addr and help functions Cong Wang
2013-07-22 7:05 ` Cong Wang
2013-07-22 7:05 ` [Patch net-next 6/7] sctp: use generic union inet_addr Cong Wang
2013-07-22 7:05 ` [Patch net-next 7/7] selinux: " Cong Wang
2013-07-22 20:36 ` Paul Moore
2013-07-23 2:07 ` Cong Wang
2013-07-22 20:44 ` [Patch net-next 0/7] net: introduce generic type and helpers for IP address Joe Perches
2013-07-23 2:00 ` Cong Wang
2013-07-23 2:16 ` Joe Perches
2013-07-23 2:26 ` Cong Wang [this message]
2013-07-24 21:28 ` David Miller
2013-07-25 12:30 ` Cong Wang
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=1374546397.24933.10.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.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.