Subject: Re: [Acpi] Re: ACPI fundamental locking problems
To: david.woolley@bts.co.uk (Dave J Woolley)
Date: Wed, 4 Jul 2001 12:03:07 +0100 (BST)
Cc: alan@lxorguk.ukuu.org.uk ('Alan Cox'), andrew.grover@intel.com,
        jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org,
        torvalds@transmeta.com, acpi@phobos.fachschaften.tu-muenchen.de
In-Reply-To: <81E4A2BC03CED111845100104B62AFB50102A7FD@stagecoach.bts.co.uk> from "Dave J Woolley" at Jul 04, 2001 11:37:00 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E15HkR1-0000lb-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> I argued this at the very beginning, but there was a very strong
> view that you needed to run most of the code before you had a user
> space to run it in.  I've not followed things closely enough to 

That bit is clearly untrue.

> My feeling has been that ACPI has violated the minimum privilege
> concept from the beginning, although I think putting stuff in drivers
> that could be at user level is not htat uncommon in Linux.

It still seems to lack even basic checks that the writes AML does are into
E820 NV or device space only - also while fixing it the ACPI guys might note
that a write close to 0xFFFFFFFF will lead to a failed ioremap and a nasty
mess because they ioremap a fixed sized window that will wrap


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