The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, ruchandani.tina@gmail.com,
	linux-afs@lists.infradead.org
Subject: Re: [PATCH 1/2] afs: Move UUID struct to linux/uuid.h
Date: Thu, 12 Jan 2017 14:14:35 +0100	[thread overview]
Message-ID: <107420020.65PPp1ZfLz@wuerfel> (raw)
In-Reply-To: <148422219487.9419.2588525606361566422.stgit@warthog.procyon.org.uk>

On Thursday, January 12, 2017 11:56:34 AM CET David Howells wrote:
> Move the afs_uuid struct to linux/uuid.h and rename it to uuid_v1.
> 
> Signed-off-by: David Howells <dhowells@redhat.com>
> 

Looks good to me, but I wonder if this part:

                r = call->request;
-               r->time_low                     = ntohl(b[0]);
-               r->time_mid                     = ntohl(b[1]);
-               r->time_hi_and_version          = ntohl(b[2]);
+               r->time_low                     = b[0];
+               r->time_mid                     = htons(ntohl(b[1]));
+               r->time_hi_and_version          = htons(ntohl(b[2]));
                r->clock_seq_hi_and_reserved    = ntohl(b[3]);
                r->clock_seq_low                = ntohl(b[4]);
 
should be considered a bugfix and split out into a
separate patch. From what I understand about the mess in UUID
formats, the time fields can either be big-endian (as defined)
or little-endian (for all things Microsoft), and you are changing
the representation from CPU-specific to big-endian, which makes
it different for x86 and most ARM at least.

	Arnd

  parent reply	other threads:[~2017-01-12 13:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 11:56 [PATCH 1/2] afs: Move UUID struct to linux/uuid.h David Howells
2017-01-12 11:56 ` [PATCH 2/2] afs: Use core kernel UUID generation David Howells
2017-01-12 13:14 ` Arnd Bergmann [this message]
2017-01-12 14:12   ` [PATCH 1/2] afs: Move UUID struct to linux/uuid.h David Howells
2017-01-12 15:40     ` Arnd Bergmann
2017-01-12 16:14       ` David Howells
2017-01-12 16:23         ` Arnd Bergmann
2017-01-12 16:40           ` David Howells
2017-01-13  9:22 ` kbuild test robot
2017-01-13 10:28   ` David Howells
2017-01-13 10:48 ` kbuild test robot

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=107420020.65PPp1ZfLz@wuerfel \
    --to=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruchandani.tina@gmail.com \
    /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