[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZpmKho9_t0_MeOP7@casper.infradead.org>
Date: Thu, 18 Jul 2024 22:35:02 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Mary Strodl <mstrodl@...edom.csh.rit.edu>,
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, christian.gmeiner@...il.com
Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range
On Thu, Jul 18, 2024 at 02:31:03PM -0700, Andrew Morton wrote:
> The hardware is weird, but we should try to support it in some fashion.
Why? It's been around since 2005, and Linux has done perfectly well
without support for it. What's so compelling about it, as compared to
ohidontknow the nVidia GPU driver where we definitely don't support
taking a binary blob of random x86 code and run it inside the kernel?
> Dumb idea, there will be other ideas: is it practical to take that code
> blob out of the BIOS, put it into a kernel module (as a .byte table in
> a .s file and suitable C interfacing), compile that up and insmod that
> module?
Have you tried asking someone who cares about security like Kees?
Preferably in person so you can take a picture of the hair on their head
standing straight out and steam coming out of their ears.
Powered by blists - more mailing lists