linux-kernel - Re: [PATCH 4/4] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface

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

Message-ID: <2025103150-subside-tux-fd46@gregkh>
Date: Fri, 31 Oct 2025 13:38:57 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Avadhut Naik <avadhut.naik@....com>, linux-edac@...r.kernel.org,
	yazen.ghannam@....com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC
 interface

On Thu, Oct 30, 2025 at 08:18:58PM +0100, Borislav Petkov wrote:
> On Thu, Oct 30, 2025 at 04:01:43PM +0100, Greg KH wrote:
> > No one is going to notice this type of kernel log message.  If you think
> > that no one is using the sysfs files, delete them now.  Why wait?
> > 
> > sysfs is meant to be such that userspace can handle file removals (i.e.
> > that value is not present.)  Unfortunately, sometimes this does not
> > actually happen and user tools do mess up and rely on things.  So either
> > no one uses the file and it can be removed now, OR you have to leave it
> > in for "forever".  There's no real chance to remove it later, that's
> > just postponing the decision.
> 
> Lemme try to repeat what you're proposing to make sure we're on the same page:
> 
> we simply zap the files and see if anyone complains. If yes, we figure out why
> they're using them and if they can't be moved to the new interface, we restore
> them and maintain them forever.
> 
> Right?

Yup!