From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751116AbdEaKdV (ORCPT ); Wed, 31 May 2017 06:33:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48018 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750992AbdEaKdT (ORCPT ); Wed, 31 May 2017 06:33:19 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 00A3681241 Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dhowells@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 00A3681241 Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20170531094157.GA10511@lst.de> References: <20170531094157.GA10511@lst.de> <20170528102008.30276-2-hch@lst.de> <20170528102008.30276-1-hch@lst.de> <9377.1496138404@warthog.procyon.org.uk> To: Christoph Hellwig Cc: dhowells@redhat.com, Andy Shevchenko , Amir Goldstein , linux-fsdevel@vger.kernel.org, Shaohua Li , Dan Williams , Steven Whitehouse , Mimi Zohar , linux-xfs@vger.kernel.org, linux-raid@vger.kernel.org, linux-nvdimm@ml01.01.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Arnd Bergmann Subject: Re: [PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22156.1496226795.1@warthog.procyon.org.uk> Date: Wed, 31 May 2017 11:33:15 +0100 Message-ID: <22157.1496226795@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 31 May 2017 10:33:19 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christoph Hellwig wrote: > Does the afs protocol require a v1 uuid or does it just use the formwat on > the wire? The format it uses on the wire is separate XDR encoding of each of the fields in the uuid_v1 struct, counting the elements of the node[] array separately. I'm not sure that the servers actually parse the contents of the UUID, but I can't be sure as I don't have access to the source for all of them. OpenAFS and AuriStor will at least accept the version field being 4, however. David