[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F613425E2@ORSMSX114.amr.corp.intel.com>
Date: Fri, 18 Aug 2017 02:12:50 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Alan Cox <gnomes@...rguk.ukuu.org.uk>
CC: "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, Boris Petkov <bp@...e.de>,
Tyler Baicar <tbaicar@...eaurora.org>,
"Punit Agrawal" <punit.agrawal@....com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ACPI / sysfs: Extend ACPI sysfs to provide access to
boot error region
> Should this not also have a capability check. Assuming file permissions
> are sufficient for grabbing a chunk of system memory holding error
> info doesn't seem too scary but it's at odds with a lot of other cases ?
At least one of those other cases (pstore) added a capability check and now regret
it. There's a thread on reverting it. Look for:
Revert "pstore: Honor dmesg_restrict sysctl on dmesg dumps"
-Tony
Powered by blists - more mailing lists