linux-kernel - Re: [PATCH 6/6 v5] regmap: Incorporate the regcache core into regmap

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:	Mon, 19 Sep 2011 17:36:23 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Dimitris Papastamos <dp@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Graeme Gregory <gg@...mlogic.co.uk>,
	Samuel Oritz <sameo@...ux.intel.com>
Subject: Re: [PATCH 6/6 v5] regmap: Incorporate the regcache core into regmap

On Mon, Sep 19, 2011 at 06:28:31PM +0200, Lars-Peter Clausen wrote:

Please delete unneeded context from mails and configure your MUA to wrap
early enough to allow for at least one level of quoting.

> On 09/19/2011 06:13 PM, Mark Brown wrote:
> > On Mon, Sep 19, 2011 at 05:57:49PM +0200, Lars-Peter Clausen wrote:

> >         if (!map->cache_bypass) {
> >                 ret = regcache_write(map, reg, val);
> > -               if (!ret || map->cache_only)
> > +               if (ret != 0)
> > +                       return ret;

> Hm... last time we said we want to fallback to hw read/write even if the cache
> operation has failed. The issue is that regcache_write will check for
> regmap_writeable, so you'll get different behaviour if caching is enabled for
> registers where regmap_writeable returns false.

I'd expect regcache_write() to silently eat such updates, though I see
it doesn't at the minute.

> >> Btw. what should happen if both cache_bypass and cache_only are set? Or is that
> >> an invalid configuration?

> > That's not sensible.  Probably BUG_ON().

> BUG_ON might be a bit to strict, if we wanted to allow cache_only to be enabled
> through debugfs like it is done for ASoC right now.

If we're going to allow those to be writable (I'm not convinced that's
sane) then it seems better that the write should enforce basic sanity.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/