[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZpkPStwq_S3mJYb5@infradead.org>
Date: Thu, 18 Jul 2024 05:49:14 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Mary Strodl <mstrodl@...edom.csh.rit.edu>,
Christoph Hellwig <hch@...radead.org>,
Mary Strodl <mstrodl@....rit.edu>, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, urezki@...il.com, linux-mm@...ck.org,
lee@...nel.org, andi.shyti@...nel.org, linux-i2c@...r.kernel.org,
s.hauer@...gutronix.de, christian.gmeiner@...il.com
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range
On Thu, Jul 18, 2024 at 01:45:11PM +0100, Matthew Wilcox wrote:
> On Thu, Jul 18, 2024 at 08:40:27AM -0400, Mary Strodl wrote:
> > On Wed, Jul 17, 2024 at 08:04:01PM -0700, Christoph Hellwig wrote:
> > > NAK to a driver creating random writable and exectutable memory:
> >
> > Is there a better way to do what I'm trying to do? Or some way to
> > expose this functionality with more guard rails so that it's a
> > little bit safer?
>
> No, there is no way to do what you're trying to do.
IFF it is absolutely required to run BIOS provided executable code,
the best way to do that is in a separate userspace process.
Powered by blists - more mailing lists