Re: [PATCH RFC] selinux: provide __le variables explicitly

2019-05-21 Thread Paul Moore
On Thu, May 9, 2019 at 3:40 PM Paul Moore wrote: > On Wed, May 8, 2019 at 8:14 PM Nicholas Mc Guire wrote: > > On Wed, May 08, 2019 at 05:47:32PM -0400, Paul Moore wrote: > > > On Wed, May 8, 2019 at 2:27 AM Nicholas Mc Guire wrote: > > > > While the endiannes is being handled properly sparse wa

Re: [PATCH RFC] selinux: provide __le variables explicitly

2019-05-09 Thread Paul Moore
On Wed, May 8, 2019 at 8:14 PM Nicholas Mc Guire wrote: > On Wed, May 08, 2019 at 05:47:32PM -0400, Paul Moore wrote: > > On Wed, May 8, 2019 at 2:27 AM Nicholas Mc Guire wrote: > > > While the endiannes is being handled properly sparse was unable to verify > > > this due to type inconsistency. S

Re: [PATCH RFC] selinux: provide __le variables explicitly

2019-05-08 Thread Nicholas Mc Guire
On Wed, May 08, 2019 at 05:47:32PM -0400, Paul Moore wrote: > On Wed, May 8, 2019 at 2:27 AM Nicholas Mc Guire wrote: > > While the endiannes is being handled properly sparse was unable to verify > > this due to type inconsistency. So introduce an additional __le32 > > respectively _le64 variable

Re: [PATCH RFC] selinux: provide __le variables explicitly

2019-05-08 Thread Paul Moore
On Wed, May 8, 2019 at 2:27 AM Nicholas Mc Guire wrote: > While the endiannes is being handled properly sparse was unable to verify > this due to type inconsistency. So introduce an additional __le32 > respectively _le64 variable to be passed to le32/64_to_cpu() to allow > sparse to verify proper

[PATCH RFC] selinux: provide __le variables explicitly

2019-05-07 Thread Nicholas Mc Guire
While the endiannes is being handled properly sparse was unable to verify this due to type inconsistency. So introduce an additional __le32 respectively _le64 variable to be passed to le32/64_to_cpu() to allow sparse to verify proper typing. Note that this patch does not change the generated binary