Re: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Rene Herman <rene.herman@...>
Cc: Jean Delvare <khali@...>, Hans de Goede <j.w.r.degoede@...>, <linux-acpi@...>, Zhang Rui <rui.zhang@...>, Mark M. Hoffman <mhoffman@...>, Linux Kernel <linux-kernel@...>, <lm-sensors@...>
Date: Monday, June 23, 2008 - 10:31 am

On Mon, Jun 23, 2008 at 02:35:03PM +0200, Rene Herman wrote:

No, libsensors made an assumption about the ABI that turns out not to be 
true. The ABI hasn't changed, libsensors is just being exposed to a case 
it didn't previously see.

We've had this kind of change before. The ACPI backlight code changed in 
such a way that scripts that blindly wrote values instead of (correctly) 
reading the maximum brightness value broke. mmap's behaviour changed in 
such a way that it was no longer possible for vm86 to execute code that 
wasn't mapped as executable, breaking libx86. The applications in 
question were undeniably buggy. Those are examples that I was personally 
involved with - I'm sure there are others. Where userspace has made 
false assumptions, it's not the kernel's responsibility to continue to 
support those assumptions.

-- 
Matthew Garrett | mjg59@srcf.ucam.org
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support..., Matthew Garrett, (Mon Jun 23, 10:31 am)