From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: allow to disable all locking mechanisms
Date: Tue, 12 Dec 2017 12:18:31 +0000 [thread overview]
Message-ID: <20171212121831.GJ16323@sirena.org.uk> (raw)
In-Reply-To: <a55c85c1-042c-d266-ebde-be4bf7324986@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
On Tue, Dec 12, 2017 at 12:42:47PM +0100, Lars-Peter Clausen wrote:
> 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.
That's true, and the debugfs is world readable too so we can't just say
it's up to root to be sensible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-12 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 14:26 Bartosz Golaszewski
2017-12-06 15:33 ` Applied "regmap: allow to disable all locking mechanisms" to the regmap tree Mark Brown
2017-12-10 13:10 ` [PATCH] regmap: allow to disable all locking mechanisms Andy Shevchenko
2017-12-10 15:14 ` Bartosz Golaszewski
2017-12-12 11:12 ` Andy Shevchenko
2017-12-12 11:25 ` Mark Brown
2017-12-12 11:42 ` Lars-Peter Clausen
2017-12-12 12:18 ` Mark Brown [this message]
2017-12-12 12:21 ` Bartosz Golaszewski
2017-12-12 15:56 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171212121831.GJ16323@sirena.org.uk \
--to=broonie@kernel.org \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®