[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9137b724-d342-4f35-b554-0e56ef37b2d9@amd.com>
Date: Tue, 5 Nov 2024 13:56:23 -0600
From: Mario Limonciello <mario.limonciello@....com>
To: Borislav Petkov <bp@...en8.de>, Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Yazen Ghannam <yazen.ghannam@....com>, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, tony.luck@...el.com, x86@...nel.org,
avadhut.naik@....com, john.allen@....com, bhelgaas@...gle.com,
Shyam-sundar.S-k@....com, richard.gong@....com, jdelvare@...e.com,
linux@...ck-us.net, clemens@...isch.de, hdegoede@...hat.com,
ilpo.jarvinen@...ux.intel.com, linux-pci@...r.kernel.org,
linux-hwmon@...r.kernel.org, platform-driver-x86@...r.kernel.org,
naveenkrishna.chatradhi@....com, carlos.bilbao.osdev@...il.com
Subject: Re: [PATCH 16/16] x86/amd_smn: Add support for debugfs access to SMN
registers
On 11/5/2024 13:53, Borislav Petkov wrote:
> On Tue, Nov 05, 2024 at 01:46:46PM -0600, Mario Limonciello wrote:
>> Why the worry about it being in debugfs by default?
>
> I want people to *actively* and *explicitly* do something before they can
> brick their systems.
>
OK got it. Considering that I think after this series lands we need to
re-open the conversation about PCI config space access to userspace;
particularly on regions that have been marked as exclusions.
By that grounds a taint is definitely not enough for that either.
Powered by blists - more mailing lists