Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1654109
| From | David Howells <dhowells@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" |
| Date | 2017-05-31 12:40 +0200 |
| Message-ID | <tN9cJ-3w7-3@gated-at.bofh.it> (permalink) |
| References | <tN8qm-31c-31@gated-at.bofh.it> <tM3Cp-Hq-1@gated-at.bofh.it> <tM3Cp-Hq-3@gated-at.bofh.it> <tMMga-5Z0-9@gated-at.bofh.it> <tN8qm-31c-31@gated-at.bofh.it> |
| 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 |
Christoph Hellwig <hch@lst.de> 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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" Christoph Hellwig <hch@lst.de> - 2017-05-28 12:30 +0200
Re: [PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" David Howells <dhowells@redhat.com> - 2017-05-30 12:10 +0200
Re: [PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" Christoph Hellwig <hch@lst.de> - 2017-05-31 11:50 +0200
Re: [PATCH 01/22] Revert "afs: Move UUID struct to linux/uuid.h" David Howells <dhowells@redhat.com> - 2017-05-31 12:40 +0200
csiph-web