linux-kernel - Re: [PATCH 1/3] iio: pressure: ms5611: fixed value compensation bug

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: <CAHp75Vd5p5tT52JA9HXaJ5opspXJJS2JECQUAUs9bqQVzc_+2Q@mail.gmail.com>
Date:   Wed, 19 Oct 2022 16:24:21 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Mitja Spes <mitja@...av.com>
Cc:     linux-iio@...r.kernel.org, Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Tomasz Duszynski <tduszyns@...il.com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] iio: pressure: ms5611: fixed value compensation bug

On Wed, Oct 19, 2022 at 3:55 PM Mitja Spes <mitja@...av.com> wrote:
>
> When using multiple instances of this driver the compensation PROM was
> overwritten by the last initialized sensor. Now each sensor has own PROM

its own

> storage.

This change is just a good example why the chip_info should always be
static const, so the volatile data should come through the different
sources.

-- 
With Best Regards,
Andy Shevchenko