forked from luck/tmp_suning_uos_patched
[PATCH] I2C: Fix incorrect sysfs file permissions in it87 and via686a drivers
The it87 and via686a hardware monitoring drivers each create a sysfs file named "alarms" in R/W mode, while they should really create it in read-only mode. Since we don't provide a store function for these files, write attempts to these files will do something undefined (I guess) and bad (I am sure). My own try resulted in a locked terminal (where I attempted the write) and a 100% CPU load until next reboot. As a side note, wouldn't it make sense to check, when creating sysfs files, that readable files have a non-NULL show method, and writable files have a non-NULL store method? I know drivers are not supposed to do stupid things, but there is already a BUG_ON for several conditions in sysfs_create_file, so maybe we could add two more? Signed-off-by: Jean Delvare <khali@linux-fr.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
parent
86b5ac878d
commit
1d66c64c3c
|
@ -668,7 +668,7 @@ static ssize_t show_alarms(struct device *dev, char *buf)
|
|||
struct it87_data *data = it87_update_device(dev);
|
||||
return sprintf(buf,"%d\n", ALARMS_FROM_REG(data->alarms));
|
||||
}
|
||||
static DEVICE_ATTR(alarms, S_IRUGO | S_IWUSR, show_alarms, NULL);
|
||||
static DEVICE_ATTR(alarms, S_IRUGO, show_alarms, NULL);
|
||||
|
||||
static ssize_t
|
||||
show_vrm_reg(struct device *dev, char *buf)
|
||||
|
|
|
@ -574,7 +574,7 @@ static ssize_t show_alarms(struct device *dev, char *buf) {
|
|||
struct via686a_data *data = via686a_update_device(dev);
|
||||
return sprintf(buf,"%d\n", ALARMS_FROM_REG(data->alarms));
|
||||
}
|
||||
static DEVICE_ATTR(alarms, S_IRUGO | S_IWUSR, show_alarms, NULL);
|
||||
static DEVICE_ATTR(alarms, S_IRUGO, show_alarms, NULL);
|
||||
|
||||
/* The driver. I choose to use type i2c_driver, as at is identical to both
|
||||
smbus_driver and isa_driver, and clients could be of either kind */
|
||||
|
|
Loading…
Reference in New Issue
Block a user