linux-kernel - Re: [lm-sensors] coretemp.0 folder contents changed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140507091308.227d8152@endymion.delvare>
Date:	Wed, 7 May 2014 09:13:08 +0200
From:	Jean Delvare <jdelvare@...e.de>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	"Yu, Fenghua" <fenghua.yu@...el.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	lm-sensors@...sensors.org
Subject: Re: [lm-sensors] coretemp.0 folder contents changed

Hi Guenter,

On Tue, 06 May 2014 06:32:15 -0700, Guenter Roeck wrote:
> Can we implement a similar approach to network devices and make hwmon
> path names (ie the /sys/class/hwmon/XXX path name) configurable via udev ?
> Might be worth exploring.

This is one possibility indeed. The good thing is that libsensors makes
no assumption on hwmon class device names, so we can change the names
without breaking any application which uses libsensors. Scripts
accessing sysfs directly may break though (pwmconfig would, for
example.)

We'll have to be careful when choosing the new names, and make sure
there is no name space collision. Network interface renaming has caused
a great deal of trouble out there.

Another approach, which I have in mind for quite some time already but
could never find the time to implement, would be a small helper binary
which would look-up hwmon devices by libsensors-like name (and the
other way around too.) Scripts could use it to benefit from libsensors
persistent names.

-- 
Jean Delvare
SUSE L3 Support
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/