linux-kernel - Re: [PATCH v5 2/7] iio: core: Refactor iio_device_claim

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <aXMrM4rDBHj0-pQU@smile.fi.intel.com>
Date: Fri, 23 Jan 2026 10:02:59 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Kurt Borja <kuurtb@...il.com>
Cc: Jonathan Cameron <jic23@...nel.org>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Michael Hennerich <Michael.Hennerich@...log.com>,
	Benson Leung <bleung@...omium.org>,
	Antoniu Miclaus <antoniu.miclaus@...log.com>,
	Gwendal Grignou <gwendal@...omium.org>,
	Shrikant Raskar <raskar.shree97@...il.com>,
	Per-Daniel Olsson <perdaniel.olsson@...s.com>,
	David Lechner <dlechner@...libre.com>,
	Nuno Sá <nuno.sa@...log.com>,
	Andy Shevchenko <andy@...nel.org>,
	Guenter Roeck <groeck@...omium.org>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
	chrome-platform@...ts.linux.dev
Subject: Re: [PATCH v5 2/7] iio: core: Refactor iio_device_claim_direct()
 implementation

On Thu, Jan 22, 2026 at 05:20:55PM -0500, Kurt Borja wrote:
> On Thu Jan 22, 2026 at 2:04 PM -05, Jonathan Cameron wrote:
> > On Tue, 20 Jan 2026 01:20:42 -0500
> > Kurt Borja <kuurtb@...il.com> wrote:

...

> > So sparse does change what it moans about with this one in precisely one instance
> > There are 9 false positives with Al Viro's updated sparse - I haven't checked the
> > original one recently.
> 
> Hi Jonathan,
> 
> Upstream sparse is kinda broken right now.

Yep, please switch to Al's version.

> I'm not getting any false positives on the locking stuff but a BUNCH of
> "error: bad constant expresion" on MODULE_*() macros so I don't fully
> trust it.
> 
> I know at least one subsystem maintainer is getting these too so I guess
> it's an upstream problem.

Yes, it's fixed in Al's version.

-- 
With Best Regards,
Andy Shevchenko