From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH] sensors-detect: Skip "random" I/O port
Date: Fri, 22 Feb 2008 07:44:04 +0000 [thread overview]
Message-ID: <20080222084404.549741f5@hyperion.delvare> (raw)
In-Reply-To: <20080218223317.2142dc16@hyperion.delvare>
On Fri, 22 Feb 2008 18:21:23 +1100, Benjamin Herrenschmidt wrote:
>
> On Fri, 2008-02-22 at 08:19 +0100, Jean Delvare wrote:
> >
> > I was referring to the kernel patch Christian submitted earlier this
> > week which prevents oopses or machine checks when older versions of
> > sensors-detect access /dev/port in unexpected ways. My update to
> > sensors-detect was meant as a complement of his patch, not a
> > replacement.
>
> But his patch can't recognize a potentially valid use of /proc/port
> right ?
I don't know much about PPC so I can't comment on the implementation.
All I'm saying is that, if it is possible at all, I believe that
preventing invalid accesses from oopsing the machine is a good idea.
> Christian, can you re-send me that patch ?
--
Jean Delvare
_______________________________________________
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-22 7:44 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 [this message]
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=20080222084404.549741f5@hyperion.delvare \
--to=khali@linux-fr.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.