linux-kernel - Re: [PATCH] regmap: fix up the regmap lock error

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

Message-ID: <20160922102309.GI7994@sirena.org.uk>
Date:   Thu, 22 Sep 2016 11:23:09 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Elaine Zhang <zhangqing@...k-chips.com>
Cc:     nikita.yoush@...entembedded.com, cphealy@...il.com,
        huangtao@...k-chips.com, xxx@...k-chips.com, jay.xu@...k-chips.com,
        linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: fix up the regmap lock error

On Thu, Sep 22, 2016 at 06:17:45PM +0800, Elaine Zhang wrote:

> Regmap lock is taken in regmap_update_bits_base() and then
> regcache_drop_region() tries to take it again.
> which added in commit 815806e39bf6
> ("regmap: drop cache if the bus transfer error")

Someone already sent a change for this.

> Backtrace:
> [<8068ab7c>] (__schedule) from [<8068b1c4>] (schedule+0xb8/0xd0)
> [<8068b10c>] (schedule) from [<8068b61c>] (schedule_preempt_disabled+0x20/0x2c)

Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative then it's
usually better to pull out the relevant sections.

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