linux-kernel - Re: [PATCH RESEND v2 1/2] regulator: include 'enabled' status in debugfs/regulator

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: <20170619165939.oa5x3irf4lfqshpq@qmqm.qmqm.pl>
Date:   Mon, 19 Jun 2017 18:59:39 +0200
From:   Michał Mirosław <mirq-linux@...e.qmqm.pl>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH RESEND v2 1/2] regulator: include 'enabled' status in
 debugfs/regulator_summary

On Mon, Jun 19, 2017 at 05:47:33PM +0100, Mark Brown wrote:
> On Mon, Jun 19, 2017 at 06:41:34PM +0200, Michał Mirosław wrote:
> > On Mon, Jun 19, 2017 at 11:17:41AM +0100, Mark Brown wrote:
> > > On Sat, Jun 17, 2017 at 11:30:12PM +0200, Michał Mirosław wrote:
> > > > Extend regulator's info line with enabled/disabled status.
> > > Why is the use count not enough information here?
> > Regulators can be enabled without any users, because of eg. always-on.
> We should probably just have always-on be incrementing the use count
> instead if it's an issue.

That's another way of tackling the issue. This file is a debuging aid, so
I prefer to see precise state information in it rather than have it hide
some special cases like this. Not a strong opinion, though.

Best Regards,
Michał Mirosław