From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O
Date: Fri, 22 Feb 2008 22:22:20 +0000 [thread overview]
Message-ID: <1203718940.6976.19.camel@pasglop> (raw)
In-Reply-To: <20080218223317.2142dc16@hyperion.delvare>
On Fri, 2008-02-22 at 11:18 +0100, Christian Krafft wrote:
> Hi Ben,
>
> regarding your problem with poking into PCI ranges:
> As arnd mentioned, we could check, wether there is a mapping for that address
> and if so, allow the access. That could be done in check_legacy_ioport,
> although the name looks a bit misleading.
> What do you think ?
It would be pretty gross to end up checking the whole device-tree
for things...
Maybe we could check that there's something in the resource tree though,
under ioport_resources, that matches the requested port.
But again, its a matter of preventing root from being stupid, which I'm
not sure is that worth pursuing...
Ben.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2008-02-22 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 21:33 [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O port probing Jean Delvare
2008-02-18 22:46 ` [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O port Benjamin Herrenschmidt
2008-02-20 19:07 ` Jean Delvare
2008-02-21 10:02 ` Christian Krafft
2008-02-21 10:09 ` Jean Delvare
2008-02-21 22:49 ` Benjamin Herrenschmidt
2008-02-22 7:19 ` Jean Delvare
2008-02-22 7:21 ` Benjamin Herrenschmidt
2008-02-22 7:44 ` Jean Delvare
2008-02-22 10:18 ` Christian Krafft
2008-02-22 21:26 ` Benjamin Herrenschmidt
2008-02-22 22:22 ` Benjamin Herrenschmidt [this message]
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=1203718940.6976.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=lm-sensors@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.