linux-kernel - Re: [PATCH] x86/vdso: shrink vdso/extable.i via IWYU

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20231229093942.GBZY6T3knaGKpeRA9a@fat_crate.local>
Date: Fri, 29 Dec 2023 10:39:42 +0100
From: Borislav Petkov <bp@...en8.de>
To: Tanzir Hasan <tanzirh@...gle.com>
Cc: Andy Lutomirski <luto@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Nick Desaulniers <nnn@...gle.com>
Subject: Re: [PATCH] x86/vdso: shrink vdso/extable.i via IWYU

On Thu, Dec 28, 2023 at 02:01:20PM -0800, Tanzir Hasan wrote:
> The intention with these changes is to add up the impact of these small changes
> over time to improve build time and also use more direct inclusions where
> possible.

The problem I see with such "changes" is that it'll be a never-ending
stream of them because over time, headers get reworked, moved, changed,
split, etc and one would have to do such reorganization again.

And I'd understand it if the benefits were higher than what you're
seeing. But right now it looks like unnecessary churn.

Dunno, perhaps one could do those in one single patch for, say,
on arch/x86/ or so, and show a before and after wrt numbers. And then do it
again in a couple of releases, when it becomes necessary again.

Or one could run that tool on patches which haven't been applied yet,
patches on lkml.

Patches which touch headers or add #include directives and then reply
with an automatic report to them, saying something along the lines of

"your patch has a suboptimal include - if you include this and that,
it'll improve build time by this and that"

and then people would incorporate those changes and right then and
there.

But let's see what the others think first.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette