linux-kernel - Re: [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE

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: <20141209161420.GJ1934@sirena.org.uk>
Date:	Tue, 9 Dec 2014 16:14:20 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Mike Looijmans <mike.looijmans@...ic.nl>
Cc:	lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] drivers/regulator/core.c: Don't print error on
 EPROBE_DEFER

On Tue, Dec 09, 2014 at 02:12:43PM +0100, Mike Looijmans wrote:
> If a regulator depends on another regulator that happens to be called
> later, the kernel always prints a message like this:
>   reg-fixed-voltage regulator_sd1: Failed to find supply vin
> Since the deferral is not something fatal, nor even something the user
> may need to be aware about, reduce the message to debug level.

No, we need to tell users if we're deferring since there's no guarantee
that the device blocking registration is ever going to be loaded - we
need to let the user know why the device isn't appearing so that they
can diagnose problems.  Yes, it's noisy and ideally we'd have something
more efficient than deferred probe but there we are.

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