From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Duane Griffin <duaneg@dghda.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
akpm@linux-foundation.org, Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] ext4: tighten restrictions on inode flags
Date: Thu, 12 Jun 2008 14:27:07 -0500 [thread overview]
Message-ID: <1213298827.6382.2.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <e9e943910806110449sbf30bf6xd98840fcd343519d@mail.gmail.com>
On Wed, 2008-06-11 at 12:49 +0100, Duane Griffin wrote:
> 2008/6/11 Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>:
> >> +/* Mask out flags that are inappropriate for the given type of inode. */
> >> +static inline __le32 ext4_mask_flags(__le16 mode, __le32 flags)
> >> +{
> >> + if (S_ISDIR(mode))
> >> + return flags;
> >> + else if (S_ISREG(mode))
> >> + return flags & ~EXT4_REG_FLMASK;
> >> + else
> >> + return flags & ~EXT4_OTHER_FLMASK;
> >> +}
> >> +
> >
> > why are the arguments __le32 ? They should be in host order.
> >
> > static inline __u32 ext4_mask_flags(umode_t mode, __u32 flags)
>
> Whoops, I was matching the fields in ex4_inode, but I should have been
> looking at ext4_inode_info. Shouldn't sparse have complained about
> that?
It does, but not by default. You need to run sparse with
-D__CHECK_ENDIAN__
I use this alias:
make_sparse is aliased to `make C=2 CF="-D__CHECK_ENDIAN__"'
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2008-06-12 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 0:04 [PATCH 0/6][v2] ext{2,3,4}: tighten inheritance and setting of inode flags Duane Griffin
2008-06-11 0:04 ` [PATCH 1/6] ext2: don't inherit inappropriate inode flags from parent Duane Griffin
2008-06-11 0:04 ` [PATCH 2/6] ext3: " Duane Griffin
2008-06-11 0:04 ` [PATCH 3/6] ext4: " Duane Griffin
2008-06-11 0:04 ` [PATCH 4/6] ext2: tighten restrictions on inode flags Duane Griffin
2008-06-11 0:04 ` [PATCH 5/6] ext3: " Duane Griffin
2008-06-11 0:04 ` [PATCH 6/6] ext4: " Duane Griffin
2008-06-11 11:31 ` Aneesh Kumar K.V
2008-06-11 11:49 ` Duane Griffin
2008-06-12 19:27 ` Dave Kleikamp [this message]
2008-06-12 20:35 ` Duane Griffin
2008-06-12 9:06 ` [PATCH 4/6] ext2: " Andreas Dilger
2008-06-12 9:38 ` Duane Griffin
-- strict thread matches above, loose matches on Subject: below --
2008-06-19 15:41 [PATCH 0/6][v3] ext{2,3,4}: tighten inheritance and setting of " Duane Griffin
2008-06-19 15:42 ` [PATCH 1/6] ext2: don't inherit inappropriate inode flags from parent Duane Griffin
2008-06-19 15:42 ` [PATCH 2/6] ext3: " Duane Griffin
2008-06-19 15:42 ` [PATCH 3/6] ext4: " Duane Griffin
2008-06-19 15:42 ` [PATCH 4/6] ext2: tighten restrictions on inode flags Duane Griffin
2008-06-19 15:42 ` [PATCH 5/6] ext3: " Duane Griffin
2008-06-19 15:42 ` [PATCH 6/6] ext4: " Duane Griffin
2008-12-03 19:54 [PATCH 0/6][REPOST] ext{2,3,4}: tighten inheritance and setting of " Duane Griffin
2008-12-03 19:54 ` [PATCH 1/6] ext2: don't inherit inappropriate inode flags from parent Duane Griffin
2008-12-03 19:54 ` [PATCH 2/6] ext3: " Duane Griffin
2008-12-03 19:55 ` [PATCH 3/6] ext4: " Duane Griffin
2008-12-03 19:55 ` [PATCH 4/6] ext2: tighten restrictions on inode flags Duane Griffin
2008-12-03 19:55 ` [PATCH 5/6] ext3: " Duane Griffin
2008-12-03 19:55 ` [PATCH 6/6] ext4: " Duane Griffin
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=1213298827.6382.2.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=duaneg@dghda.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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