All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: andrew.grover@intel.com, linux-kernel@vger.kernel.org,
	acpi@phobos.fachschaften.tu-muenchen.de
Subject: Re: ACPI fundamental locking problems
Date: Tue, 10 Jul 2001 00:44:49 +0200	[thread overview]
Message-ID: <20010710004449.B557@bug.ucw.cz> (raw)
In-Reply-To: <3B421AEA.8809D11C@mandrakesoft.com> <E15HW0o-0008FJ-00@the-village.bc.nu>
In-Reply-To: <E15HW0o-0008FJ-00@the-village.bc.nu>; from Alan Cox on Tue, Jul 03, 2001 at 08:39:06PM +0100

Hi!

> > The difference with ACPI is that vendors can write code that is executed
> > in the kernel's context (instead of what you can consider the BIOS's
> > context).  That is a whole new can of worms.
> 
> For security reasons alone we need to ensure ACPI can be firmly in the off
> position. Executing US written binary code in the Linux kernel will not be
> acceptable to european corporations, non US military bodies and most 
> Governments. They'd hate the US to get prior warning of say protestors
> walking into their top secret menwith hill base playing the mission impossible
> theme tune then chaining themselves to things..
> 
> And if the NSA wants the US goverment to execute binary only chinese bios code
> on all their critical systems I am sure people will be happy.

...but I still would be happier if there was no AML interpretation...
								Pavel 
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-07-10 19:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 18:54 ACPI fundamental locking problems Grover, Andrew
2001-07-03 19:08 ` Alan Cox
2001-07-03 19:20 ` Jeff Garzik
2001-07-03 19:39   ` Alan Cox
2001-07-09 22:44     ` Pavel Machek
2001-07-12 21:27       ` Alan Cox
2001-07-09 22:44     ` Pavel Machek [this message]
2001-07-03 19:37 ` Dave Jones
2001-07-03 19:37 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-07-03 22:01 Grover, Andrew
2001-07-03 21:28 Grover, Andrew
2001-07-03 21:37 ` Alan Cox
2001-07-03 21:53 ` arjan
2001-07-03 17:55 Jeff Garzik
2001-07-03 19:10 ` Johannes Erdfelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010710004449.B557@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=acpi@phobos.fachschaften.tu-muenchen.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.