linux-kernel - Re: Using regmap_update_bits to update a write only register

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-next>] [day] [month] [year] [list]

Message-ID: <20150306112142.GG21293@sirena.org.uk>
Date:	Fri, 6 Mar 2015 11:21:42 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Daniel Baluta <daniel.baluta@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Using regmap_update_bits to update a write only register

On Thu, Mar 05, 2015 at 08:14:14PM +0200, Daniel Baluta wrote:
> On Mar 5, 2015 7:54 PM, "Mark Brown" <broonie@...nel.org> wrote:

> > Probably, or there's a bug.  What should happen is that if the register
> > default appeared successfully then the read will get statisfied from the
> > cache in the manner you describe - presumably that's gone wrong somehow.
> > Have you set num_reg_defaults?  That's the obvious thing...

> Did that. I will have a closer look. Thanks for the answer.

OK, the other thing that springs to mind to check is that the register
didn't somehow get marked as volatile.

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