[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y9pno7gZHa+r/Rg3@kadam>
Date: Wed, 1 Feb 2023 16:22:43 +0300
From: Dan Carpenter <error27@...il.com>
To: David Laight <David.Laight@...lab.com>
Cc: 'Guru Mehar Rachaputi' <gurumeharrachaputi@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-staging@...ts.linux.dev" <linux-staging@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: pi433: modify bit_rate from u16 to u32
On Wed, Feb 01, 2023 at 12:34:50PM +0000, David Laight wrote:
> In reality having a uapi structure with embedded padding should
> be banned.
> But that would need a compiler attribute to enforce it.
It would be simple enough to grep the names of all the UAPI struct and
use pahole to make a list of the existing structs which have holes.
Then re-run the script every week and complain when new holey struct
types are added.
You could do a similar thing with Smatch looking at copy_to/from_user()
struct types.
regards,
dan carpenter
Powered by blists - more mailing lists