linux-kernel - Re: [PATCH] regmap: Add debugfs file for forcing field writes

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

Message-ID: <384ff7cd-4042-4e6e-89e6-356e9b37aee4@sirena.org.uk>
Date:   Tue, 13 Jun 2023 12:06:03 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Waqar Hameed <waqar.hameed@...s.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-kernel@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH] regmap: Add debugfs file for forcing field writes

On Tue, Jun 13, 2023 at 12:24:28PM +0200, Waqar Hameed wrote:
> On Mon, Jun 12, 2023 at 16:00 +0100 Mark Brown <broonie@...nel.org> wrote:
> 
> > If we're going to do something like this which could interfere with
> > driver operation then it should be guarded like the write support is so
> > that people using it have to modify the kernel to get the feature, or at
> > the very least taint the kernel.  This is less invasive but still might
> > cause issues if someone is relying on read/modify/write behaviour.

> I understand your point. Should we introduce a new macro like
> `REGMAP_ALLOW_WRITE_DEBUGFS` (which requires direct code modification to
> enable it) to guard this or introduce a new kernel configuration?

I'd add a macro.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)