linux-kernel - Re: [PATCH] regmap: allow to disable all locking mechanisms

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: <a55c85c1-042c-d266-ebde-be4bf7324986@metafoo.de>
Date:   Tue, 12 Dec 2017 12:42:47 +0100
From:   Lars-Peter Clausen <lars@...afoo.de>
To:     Bartosz Golaszewski <brgl@...ev.pl>,
        Mark Brown <broonie@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: allow to disable all locking mechanisms

On 12/06/2017 03:26 PM, Bartosz Golaszewski wrote:
[...]
> + * @disable_locking: This regmap is either protected by external means or
> + *                   is guaranteed not be be accessed from multiple threads.

To guarantee this you need to make sure that a regmap instance with this
flag set does not register a debugfs interface. debugfs file access happens
from a userspace process and hence could (and probably) is in a different
thread than the driver regmap access.