linux-kernel - Re: [PATCH next 11/14] bit: Strengthen compile-time tests in GENMASK() and BIT()

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: <aXM1bWepP2sVy9qA@smile.fi.intel.com>
Date: Fri, 23 Jan 2026 10:46:37 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Vincent Mailhol <mailhol@...nel.org>
Cc: Al Viro <viro@...iv.linux.org.uk>, Chris Li <sparse@...isli.org>,
	Philip Li <philip.li@...el.com>,
	David Laight <david.laight.linux@...il.com>,
	kernel test robot <lkp@...el.com>,
	Nathan Chancellor <nathan@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Arnd Bergmann <arnd@...db.de>, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org, Yury Norov <yury.norov@...il.com>,
	Jani Nikula <jani.nikula@...el.com>,
	Kees Cook <keescook@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	oe-kbuild-all@...ts.linux.dev,
	Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [PATCH next 11/14] bit: Strengthen compile-time tests in
 GENMASK() and BIT()

On Fri, Jan 23, 2026 at 09:32:39AM +0100, Vincent Mailhol wrote:
> On 23/01/2026 at 09:24, Andy Shevchenko wrote:
> > On Fri, Jan 23, 2026 at 08:20:27AM +0000, Al Viro wrote:
> >> On Fri, Jan 23, 2026 at 10:11:19AM +0200, Andy Shevchenko wrote:

...

> >>>> Al Viro's fork just adds 8 commit on top of the upstream sparse repo.
> >>>> Wouldn't it be possible to just merge those?
> >>>
> >>> Ideally yes, but you also should kick the distro's asses to update it, and
> >>> the sparse should bump its version...
> >>>
> >>>> That would be much less confusing.
> >>>
> >>> Seems Al become a sparse maintainer de facto :-)
> >>
> >> Huh?  What happened to Chris?
> 
> After the project hiatus, I can imagine that there is some confusion :)
> 
> But Chris is back in his role of maintainer since September 2025. See:
> 
>   - https://lore.kernel.org/linux-sparse/CACePvbXDO1ZybDu3RaFhED9D-9gC6LTMpWrxoh5xD+ZO5SLdzA@mail.gmail.com/
>   - https://git.kernel.org/pub/scm/devel/sparse/sparse.git/commit/?id=67f0a03cee4637e495151c48a02be642a158cbbb
> 
> > I don't know, but upstream sparse haven't applied any solution for
> > MODULE*("FOO") stuff, nor reaction on my ping in that discussion
> > (I did it like week or so ago).

My ping: https://lore.kernel.org/all/aV9vo7_turBr84bs@black.igk.intel.com/
But now I realised that there was another version of the series, and Chris
seems active there.
https://lore.kernel.org/all/CACePvbU5Pqo=bw_j8arOq16o1JBOSwPtuMZBVozy4FV7YsSLGw@mail.gmail.com/

> I am out of context here, but were the correct people CCed?

I dunno.

-- 
With Best Regards,
Andy Shevchenko