linux-kernel - Re: [PATCH] regulator: of: Lower the severity of the error with no container

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Oct 2014 01:12:13 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
	linaro-kernel@...ts.linaro.org, atull@...nsource.altera.com
Subject: Re: [PATCH] regulator: of: Lower the severity of the error with no
 container

On Wed, Oct 08, 2014 at 05:05:55PM -0700, Guenter Roeck wrote:
> On Thu, Oct 09, 2014 at 12:45:41AM +0100, Mark Brown wrote:

> > definitely at least add a boot argument or something to suppress them,
> > let me have a think if we want to do that by default.

> It is a nuisance, so I might just disable it in our tree if we don't
> find some other solution.

We'll do something, just a question of what and what the default is.

> Did you notice the problem with debugfs I had mentioned earlier ?
> With all those regulators, not all of them being used, I end up with
> many having the same name. This causes issues with debugfs, which is
> trying to create the same file several times.

> Any idea how we could solve this ? The constraints message is annoying,
> but this one is a real issue.

Shove a dev_name() on the front if we get a collision?  I have to say
I've never cared, the debugfs isn't that important so it doesn't matter
too much if it fails.

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