linux-kernel - Re: [PATCH] tty: max310x: work around regmap->regcache data corruption

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: <9d3bdd33-cc23-4c80-a120-68898ba0c572@sirena.org.uk>
Date:   Tue, 5 Dec 2023 16:00:07 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Hugo Villeneuve <hugo@...ovil.com>
Cc:     Jan Kundrát <jan.kundrat@...net.cz>,
        Cosmin Tanislav <cosmin.tanislav@...log.com>,
        linux-serial@...r.kernel.org,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tty: max310x: work around regmap->regcache data
 corruption

On Tue, Dec 05, 2023 at 10:52:46AM -0500, Hugo Villeneuve wrote:

> after our discussion about regmap range, it seems that the
> efr_lock will need to stay.

OK.

> In fact, all of this helped me to uncover another case where an
> additional lock would be needed.

Some progress at least!

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