linux-kernel - Re: Loading DSDT from initrd, can it be done from grub instead?

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: <54484.145.64.134.222.1211286021.squirrel@www.hardeman.nu>
Date:	Tue, 20 May 2008 14:20:21 +0200 (CEST)
From:	David Härdeman <david@...deman.nu>
To:	"Alan Jenkins" <aj504@...york.ac.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Loading DSDT from initrd, can it be done from grub instead?

On Tue, May 20, 2008 13:58, Alan Jenkins wrote:
> David Härdeman wrote:
>> In commit 9a9e0d685553af76cb6ae2af93cca4913e7fcd47 the
>> ACPI_CUSTOM_DSDT_INITRD option was removed.
>>
>> I was wondering if it'd be feasible to hack grub to load a custom DSDT
>> instead (since grub can read filesystems) and then pass a pointer to a
>> memory location containing the DSDT to the kernel?
>
> Um, why?  What stops you from reverting the offending commit?

Because doing it from grub (if possible) would allow custom DSDT's to be
loaded without patching the kernel (e.g. allows distro kernels to be used)
and without introducing code that opens files from kernel space and mucks
with both the VFS and ACPI in ugly ways?

> Without further info, I'd assume the feature was removed on policy
> grounds.  I.e. it's not nice to be effectively patching the BIOS
> yourself, and vendors have fixed most of their BIOS's / linux is
> slightly more tolerant to broken ones. I don't know whats wrong with
> reading files from the initrd.

If you do not understand the issue at hand, why comment?

-- 
David Härdeman

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/