public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ricardo Biehl Pasquali
	<pasqualirb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ip.7: INADDR_* values cannot be assigned directly to s_addr
Date: Mon, 18 Dec 2017 17:42:40 +0100	[thread overview]
Message-ID: <0f994a1a-a6af-c795-735d-ab07107d41bc@gmail.com> (raw)
In-Reply-To: <20171214211815.GA4844-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Hello Ricardo,

On 12/14/2017 10:18 PM, Ricardo Biehl Pasquali wrote:
> Signed-off-by: Ricardo Biehl Pasquali <pasqualirb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Thanks. I applid you patch, but then also did 
s/INADDR_ANY/INADDR_LOOPBACK/ in the first sentence that you
changed. INADDR_LOOPBACK is a better example, since it is not
byte-order neutral.

Cheers,

Michael


> ---
> 
> According to The Open Group Base Specifications Issue 7, RATIONALE
> section of <http://pubs.opengroup.org/onlinepubs/9699919799/
> basedefs/netinet_in.h.html> some INADDR_* values must be converted
> using htonl().
> 
> INADDR_ANY and INADDR_BROADCAST are byte-order-neutral so they do
> not require htonl(), however I only comment this fact in NOTES.
> On the text I recommend to use htonl(), "even if for some subset
> it's not necessary".
> 
> Proof code:
> 	#include <arpa/inet.h> /* inet_addr() htonl() */
> 	#include <inttypes.h> /* PRIu32 */
> 	#include <netinet/in.h> /* INADDR_* */
> 	#include <stdio.h> /* printf() */
> 
> 	#define LOOPBACK_ADDRESS  "127.0.0.1"
> 
> 	int
> 	main(void)
> 	{
> 		/* uint32_t as defined in the former
> 		 * specification */
> 		uint32_t addr;
> 
> 		addr = inet_addr(LOOPBACK_ADDRESS);
> 
> 		printf("inet_addr:              %" PRIu32 "\n"
> 		       "htonl(INADDR_LOOPBACK): %" PRIu32 "\n"
> 		       "INADDR_LOOPBACK:        %" PRIu32 "\n",
> 		       addr, htonl(INADDR_LOOPBACK),
> 		       INADDR_LOOPBACK);
> 
> 		return 0;
> 	}
> 
> 		Ricardo Biehl Pasquali
> 
>  man7/ip.7 | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/man7/ip.7 b/man7/ip.7
> index d05d211..d7481e2 100644
> --- a/man7/ip.7
> +++ b/man7/ip.7
> @@ -193,8 +193,11 @@ contains the host interface address in network byte order.
>  .I in_addr
>  should be assigned one of the
>  .BR INADDR_*
> -values (e.g.,
> +values
> +(e.g.,
>  .BR INADDR_ANY )
> +using
> +.BR htonl (3)
>  or set using the
>  .BR inet_aton (3),
>  .BR inet_addr (3),
> @@ -1267,6 +1270,13 @@ Using the
>  socket options level isn't portable; BSD-based stacks use the
>  .B IPPROTO_IP
>  level.
> +.PP
> +.B INADDR_ANY
> +(0.0.0.0) and
> +.B INADDR_BROADCAST
> +(255.255.255.255) are byte-order-neutral. That means
> +.BR htonl (3)
> +has no effect on them.
>  .SS Compatibility
>  For compatibility with Linux 2.0, the obsolete
>  .BI "socket(AF_INET, SOCK_PACKET, " protocol )
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2017-12-18 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 21:18 [PATCH] ip.7: INADDR_* values cannot be assigned directly to s_addr Ricardo Biehl Pasquali
     [not found] ` <20171214211815.GA4844-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-12-18 16:42   ` Michael Kerrisk (man-pages) [this message]

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=0f994a1a-a6af-c795-735d-ab07107d41bc@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pasqualirb-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox