linux-kernel - Re: [PATCH v1 1/1] regmap-irq: Consistently use memset32() in regmap_irq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ZvPRpmaUuR3JlUYY@smile.fi.intel.com>
Date: Wed, 25 Sep 2024 12:02:30 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Matti Vaittinen <mazziesaccount@...il.com>
Cc: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v1 1/1] regmap-irq: Consistently use memset32() in
 regmap_irq_thread()

On Wed, Sep 25, 2024 at 11:55:51AM +0300, Matti Vaittinen wrote:
> On 9/25/24 11:27, Andy Shevchenko wrote:

...

> >   		memset32(data->status_buf, GENMASK(31, 0), chip->num_regs);

> > -		memset(data->status_buf, 0, size);
> > +		memset32(data->status_buf, 0, chip->num_regs);

> Can we guarantee the sizeof(unsigned int) == sizeof(uint32_t) on all
> supported architectures? (The status_buf is unsigned int, right?). If yes,
> then this looks nice to me.

Yes as long as we (Linux kernel) support only 32-bit and higher architectures.

-- 
With Best Regards,
Andy Shevchenko