linux-kernel - Re: userspace regression with hwmon

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] [day] [month] [year] [list]

Message-ID: <20170627153403.18f1f09e@endymion>
Date:   Tue, 27 Jun 2017 15:34:03 +0200
From:   Jean Delvare <jdelvare@...e.de>
To:     Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org,
        Fenghua Yu <fenghua.yu@...el.com>, linux-hwmon@...r.kernel.org
Subject: Re: userspace regression with hwmon

On Tue, 27 Jun 2017 05:52:39 -0700, Guenter Roeck wrote:
> On 06/27/2017 05:23 AM, Sudip Mukherjee wrote:
> > Well, using the raw platform device path was a bad design decision.
> > But I still see a difference. In v3.8 all the temp* nodes were in
> > /sys/class/hwmon/hwmon0/device/ but in v4.4 I can see that they are in
> > /sys/class/hwmon/hwmon0/. So if we do modify the code, then we still
> > need to have two versions of userspace code based on the kernel.
> 
> Your code should check for the 'name' attribute in both locations.

... as libsensors does. If you just do what libsensors does, you'll be
on the safe side.

-- 
Jean Delvare
SUSE L3 Support