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: <aXMwIcH7Zh-1yNq3@smile.fi.intel.com>
Date: Fri, 23 Jan 2026 10:24:01 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Vincent Mailhol <mailhol@...nel.org>, Philip Li <philip.li@...el.com>,
	Chris Li <sparse@...isli.org>,
	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 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?

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).

> FWIW, I do have some followups to that series
> sitting locally; need to get that finished (mostly for proper __VA_OPT__
> handling; that got stalled on the lovely corner cases where the interplay
> with side effects of macro expansion is really nasty - gcc and clang do
> not agree and gcc is arguably buggy) and posted.

Thanks for doing all this!

> I've done quite a bit of sparse work over the years, but I would rather
> prefer somebody else as overall maintainer, TYVM...


-- 
With Best Regards,
Andy Shevchenko