linux-kernel - Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node

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: <ZppfQFdwYq-bf9Wv@casper.infradead.org>
Date: Fri, 19 Jul 2024 13:42:40 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Mary Strodl <mstrodl@...edom.csh.rit.edu>
Cc: Christian Gmeiner <christian.gmeiner@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@...radead.org>,
	Mary Strodl <mstrodl@....rit.edu>, linux-kernel@...r.kernel.org,
	urezki@...il.com, linux-mm@...ck.org, lee@...nel.org,
	andi.shyti@...nel.org, linux-i2c@...r.kernel.org,
	s.hauer@...gutronix.de
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range

On Fri, Jul 19, 2024 at 07:58:40AM -0400, Mary Strodl wrote:
> Maybe some of the stuff the driver does right now could be moved into
> vmalloc? In other words, we could provide a different function that
> allocates an executable page, copies memory into it, then marks it
> read-only. Would that do better to alleviate concerns?

No.  We are not running arbitrary x86 code.  That is a security
nightmare.