linux-kernel - Re: [PATCH] um: Support SPARSE

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: <aK9faES_JZYCgyip@google.com>
Date: Wed, 27 Aug 2025 12:41:28 -0700
From: Brian Norris <briannorris@...omium.org>
To: Johannes Berg <johannes@...solutions.net>
Cc: Richard Weinberger <richard@....at>,
	Anton Ivanov <anton.ivanov@...bridgegreys.com>,
	linux-um@...ts.infradead.org, linux-kernel@...r.kernel.org,
	David Gow <davidgow@...gle.com>, Sinan Nalkaya <sardok@...il.com>
Subject: Re: [PATCH] um: Support SPARSE_IRQ

On Wed, Aug 27, 2025 at 09:38:17PM +0200, Johannes Berg wrote:
> On Mon, 2025-08-25 at 14:19 -0700, Brian Norris wrote:
> > 
> > +#ifdef CONFIG_SPARSE_IRQ
> > +int __init arch_probe_nr_irqs(void)
> > 
> 
> Is there much point in the ifdef if it's anyway always going to be
> enabled due to the 'select'?

Oh, good question. No, I don't see much point. I think I was waffling
about the MAY_HAVE_SPARSE_IRQ question, but if we go with 'select
SPARSE_IRQ' as proposed, I should probably drop the #ifdef.

Will send v2 if that's the only question/request.

Brian