From: "Theodore Ts'o" <tytso@mit.edu>
To: Alex Williamson <alex.williamson@hp.com>
Cc: "Yu, Luming" <luming.yu@intel.com>,
Dmitry Torokhov <dtor_core@ameritech.net>,
acpi-devel@lists.sourceforge.net, "Keshavamurthy,
Anil S" <anil.s.keshavamurthy@intel.com>,
"Brown, Len" <len.brown@intel.com>,
LHNS list <lhns-devel@lists.sourceforge.net>,
Linux IA64 <linux-ia64@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] PATCH-ACPI based CPU hotplug[2/6]-ACPI Eject interfacesupport
Date: Tue, 21 Sep 2004 13:25:46 -0400 [thread overview]
Message-ID: <20040921172546.GA7077@thunk.org> (raw)
In-Reply-To: <1095735738.3920.29.camel@mythbox>
On Mon, Sep 20, 2004 at 09:02:18PM -0600, Alex Williamson wrote:
> > But, some AML methods are risky to be called directly from user space,
> > Not only because the side effect of its execution, but also because
> > it could trigger potential AML method bug or interpreter bug, or even
> > architectural defect. All of these headache is due to the AML method
> > is NOT intended for being used by userspace program.
>
> I've made an attempt to hide the most obvious dangerous methods, but
> undoubtedly, there will be some. Why are we any more likely to hit an
> AML method bug, interpreter bug or architectural bug by having a
> userspace interface?
As long as the userspace interfaces are only available to the root
filesystem, I'm not sure it's worth it to hide any of the methods.
It's added complexity, and in any case, root can do untold amounts of
damage by writing to /dev/mem, trying to upload firmware to IDE
drives, etc., etc., etc.
As you have pointed out, if there are bugs in the interpret, et. al,
it is better to expose them sooner rather than to stick our heads in
the sand and pretend they don't exist.
- Ted
next prev parent reply other threads:[~2004-09-21 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 2:30 [ACPI] PATCH-ACPI based CPU hotplug[2/6]-ACPI Eject interfacesupport Yu, Luming
2004-09-21 3:02 ` Alex Williamson
2004-09-21 17:25 ` Theodore Ts'o [this message]
2004-09-21 18:10 ` Alex Williamson
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=20040921172546.GA7077@thunk.org \
--to=tytso@mit.edu \
--cc=acpi-devel@lists.sourceforge.net \
--cc=alex.williamson@hp.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dtor_core@ameritech.net \
--cc=len.brown@intel.com \
--cc=lhns-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox