From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O port
Date: Thu, 21 Feb 2008 22:49:18 +0000 [thread overview]
Message-ID: <1203634158.10422.198.camel@pasglop> (raw)
In-Reply-To: <20080218223317.2142dc16@hyperion.delvare>
On Thu, 2008-02-21 at 11:09 +0100, Jean Delvare wrote:
> On Thu, 21 Feb 2008 11:02:55 +0100, Christian Krafft wrote:
> > I will try to test your patch today, but only have a little time for this.
> > If I'm not getting it today, I'll continue next monday.
>
> Note that I managed to test the SVN version of sensors-detect myself
> (on ppc64) so I am confident that it works well now.
>
> > I'm not very convinced, that this is the right solution, but as a
> > circumvention, it will take the pressure away.
>
> What do you think would be the right solution? I agree that
> making /dev/port access safer at the kernel level is still needed. Do
> you have anything else in mind?
"safer" how so ?
How can the kernel differenciate between valid and non valid uses of
it ?
Ben.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-02-21 22:49 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 [this message]
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 ` [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O Benjamin Herrenschmidt
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=1203634158.10422.198.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.