From: Stelian Pop <stelian.pop@fr.alcove.com>
To: "J.D. Hood" <jdthood@yahoo.co.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PnPBIOS 2.4.9-ac1[56] Vaio fix
Date: Tue, 2 Oct 2001 10:35:39 +0200 [thread overview]
Message-ID: <20011002103539.D25153@come.alcove-fr> (raw)
In-Reply-To: <20011001154136.K5531@come.alcove-fr> <20011001192104.17249.qmail@web10307.mail.yahoo.com>
In-Reply-To: <20011001192104.17249.qmail@web10307.mail.yahoo.com>
On Mon, Oct 01, 2001 at 08:21:04PM +0100, J.D. Hood wrote:
> However, if is_sony_vaio_laptop is 0 at pnpbios init
> time then if you look in /proc/bus/pnp you'll see numerical
> entries there.
Yes:
# cd /proc/bus/pnp/
# ls
00 01 02 03 04 05 06 07 08 09 0b 0c 0d 0e boot devices
# ls boot
00 01 02 03 04 05 06 07 08 09 0b 0c 0d 0e
> Want to crash your machine? Just read from
> them. (The numerically named entries in /proc/bus/pnp/boot
> should be okay to read and write, though.)
It doesn't crash. I did a "cat /proc/bus/pnp/0* > /dev/null"
and the laptop is still alive.
> We need to know when is_sony_vaio_laptop so that we can
> stop this from happening.
See above.
> So either we put the dmi scan
> earlier (which Alan says is in the works)
This is the solution, as Alan said DMI idents will be needed for
some other boards (GX ?).
Alan: are you already working on this or you're waiting for a
patch ?
> or else we allow
> the creation of the proc entries at init time but reject
> read/write accesses after init time. I'll make up a patch
> that does the latter, but it would be nicest if the proc
> entries were omitted altogether.
If we cannot read nor write them, there is no point in showing
them... (we already have the devices file to show the list).
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|
next prev parent reply other threads:[~2001-10-02 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 12:54 Thomas Hood
2001-10-01 13:41 ` Stelian Pop
2001-10-01 19:21 ` J.D. Hood
2001-10-02 8:35 ` Stelian Pop [this message]
2001-10-01 13:44 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 15:15 Thomas Hood
2001-10-02 13:37 Thomas Hood
2001-10-02 1:54 Thomas Hood
2001-09-30 17:46 Thomas Hood
2001-10-01 10:04 ` Stelian Pop
2001-10-01 13:50 ` St?phane List
2001-09-29 0:29 Thomas Hood
2001-09-29 0:28 Thomas Hood
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=20011002103539.D25153@come.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jdthood@yahoo.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®