linux-kernel - Re: [PATCH 0/4] Remove problematic include in <asm/set

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: <490f7554-62eb-48a3-a45d-a65e68794b58@arm.com>
Date: Wed, 11 Dec 2024 09:14:07 +0100
From: Kevin Brodsky <kevin.brodsky@....com>
To: Christoph Hellwig <hch@...radead.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, bp@...en8.de,
 dan.j.williams@...el.com, dave.hansen@...ux.intel.com, david@...hat.com,
 jane.chu@...cle.com, osalvador@...e.de, tglx@...utronix.de
Subject: Re: [PATCH 0/4] Remove problematic include in <asm/set_memory.h>

On 11/12/2024 06:04, Christoph Hellwig wrote:
> On Tue, Dec 10, 2024 at 06:46:06PM +0000, Kevin Brodsky wrote:
>> The need for this series arose from a completely unrelated series [1].
>> Long story short, that series causes <linux/mm.h> to include
>> <linux/set_memory.h>, which doesn't feel too unreasonable.
> It is entirely unreasoable. <linux/mm.h> is inclued just about
> everywhere and should not grow more fringe includes.

Understood, I did wonder about that. Then I suppose the best course of
action for the problematic patch in that other series [3] is to move
pagetable_{alloc,free} out of linux/mm.h.

- Kevin

[3]
https://lore.kernel.org/linux-hardening/20241206101110.1646108-11-kevin.brodsky@arm.com/