linux-kernel - [PATCH 0/3] hwmon: (nct6775) Support lock by ACPI mutex

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

Message-Id: <20211122212850.321542-1-pauk.denis@gmail.com>
Date:   Mon, 22 Nov 2021 23:28:47 +0200
From:   Denis Pauk <pauk.denis@...il.com>
To:     unlisted-recipients:; (no To-header on input)
Cc:     eugene.shalygin@...il.com, andy.shevchenko@...il.com,
        pauk.denis@...il.com, platform-driver-x86@...r.kernel.org,
        thomas@...ssschuh.net, Guenter Roeck <linux@...ck-us.net>,
        Jean Delvare <jdelvare@...e.com>, linux-hwmon@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] hwmon: (nct6775) Support lock by ACPI mutex

Lock by ACPI mutex that is required for support ASUS MAXIMUS VII HERO 
motherboard. In other case, all methods are returned zero instead of real 
values. Code uses acpi mutex before any IO operations in case when such 
acpi mutex is known.

Patch series adds additional check for ChipID, and if method returned 
zero, all calls by acpi_wmi are disabled. 

Could you please review? Is it correct usage of ACPI mutex or better 
to use some other method for reuse same ACPI mutex?

---

Denis Pauk (3):
  hwmon: (nct6775) Use nct6775_*() lock function pointers in
    nct6775_data.
  hwmon: (nct6775) Implement custom lock by ACPI mutex.
  hwmon: (nct6775) add MAXIMUS VII HERO.

 drivers/hwmon/nct6775.c | 358 +++++++++++++++++++++++++++++-----------
 1 file changed, 259 insertions(+), 99 deletions(-)

base-commit: fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf
-- 
2.33.0