linux-kernel - Provide /sys/../ec with read/write access and some cleanups

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: <1277996570-2686-1-git-send-email-trenn@suse.de>
Date:	Thu,  1 Jul 2010 17:02:44 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	lenb@...nel.org
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	platform-driver-x86@...r.kernel.org, astarikovskiy@...e.de
Subject: Provide /sys/../ec with read/write access and some cleanups

These patches are diffed against the test branch of the ACPI tree, but also
patch fine with 2.6.35-rc3.

I thought about tainting the kernel if someone writes to the EC, but as
userspace can also write to graphics IO, PCI config or MSRs, it shouldn't
matter that much.
Eventually this should still be added (by a separate patch), one can easily
confuse the EC to not switch on the fans anymore.

A small tool to read out and write to /sys/devices/system/ec/*/io can be
found here:
ftp://ftp.suse.com/pub/people/trenn/sources/ec/ec_access.c

Len: Can you apply these into your test branch and schedule them for linux-next
and 2.6.36 if there are no objections, please.

Thanks,

     Thomas

--
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/