Messages in this thread |  | | | Date | Thu, 9 Nov 2006 08:27:33 +0300 | | From | Alexey Dobriyan <> | | Subject | Re: [PATCH 1/1] security: introduce fs caps |
| |
On Wed, Nov 08, 2006 at 05:52:03PM -0600, Serge E. Hallyn wrote: > > > + __u32 version; > > > + __u32 effective; > > > + __u32 permitted; > > > + __u32 inheritable; > > > +}; > > > + > > > +static inline void convert_to_le(struct vfs_cap_data_struct *cap) > > > +{ > > > + cap->version = le32_to_cpu(cap->version); > > > + cap->effective = le32_to_cpu(cap->effective); > > > + cap->permitted = le32_to_cpu(cap->permitted); > > > + cap->inheritable = le32_to_cpu(cap->inheritable); > > > +} > > > > This pretty much defeats sparse endian checking. You will get warnings > > regardless of whether u32 or le32 are used. > > But I don't get any sparse warnings with make C=1. Am I doing something > wrong?
You need (temporarily) to use CF:
make C=1 CF=-D__CHECK_ENDIAN__ ...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |