From: Alexey Dobriyan <adobriyan@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, Steven French <sfrench@us.ibm.com>
Subject: Fwd: Re: [patch 1/3] __leify posix_acl_xattr_entry, posix_acl_xattr_header
Date: Wed, 22 Jun 2005 22:46:32 +0400 [thread overview]
Message-ID: <200506222246.32763.adobriyan@gmail.com> (raw)
Christoph, can you comment on what Steve said to my patch which is exactly
the same as yours acl-endianess-annotations.patch?
============================================================================
From: Steven French <sfrench@us.ibm.com>
You may be correct, but making the in memory representations of these
structions little endian seems wrong and I would be surprised if it were
little endian, but I have not had time to think through what happens when a
local filesystem takes an existing hard drive with ACLs on various inodes
and moves the drive from a little endian to a big endian machine and the
endian implications on this structure.
Although the representation on the wire for the cifs protocol is clearly
little endian for the acl entries, I am uncomfortable with changes to the
in memory representation until I do more checking.
============================================================================
--- 25/include/linux/posix_acl_xattr.h~acl-endianess-annotations
+++ 25-akpm/include/linux/posix_acl_xattr.h
@@ -23,13 +23,13 @@
#define ACL_UNDEFINED_ID (-1)
typedef struct {
- __u16 e_tag;
- __u16 e_perm;
- __u32 e_id;
+ __le16 e_tag;
+ __le16 e_perm;
+ __le32 e_id;
} posix_acl_xattr_entry;
typedef struct {
- __u32 a_version;
+ __le32 a_version;
posix_acl_xattr_entry a_entries[0];
} posix_acl_xattr_header;
next reply other threads:[~2005-06-22 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 18:46 Alexey Dobriyan [this message]
2005-06-26 12:34 ` Fwd: Re: [patch 1/3] __leify posix_acl_xattr_entry, posix_acl_xattr_header Christoph Hellwig
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=200506222246.32763.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@us.ibm.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 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.