linux-kernel - Re: [GIT PULL] Pin control fixes for v6.7 minus one patch

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: <CAHk-=whZj3WZezdj8wq6thUeRfzua2y2QsrnoPG9dqfmk-=rcw@mail.gmail.com>
Date:   Wed, 29 Nov 2023 07:48:17 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Maria Yu <quic_aiquny@...cinc.com>,
        Charles Keepax <ckeepax@...nsource.cirrus.com>
Subject: Re: [GIT PULL] Pin control fixes for v6.7 minus one patch

On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@...aro.org> wrote:
>
> Here is an updated tag on a branch where the only change
> is to drop the locking READ_ONCE() patch until we know
> more about what is going on here.

Bah. I already pulled the previous one and pushed out before reading
more emails and noticing you had so quickly re-done it.

So the READ_ONCE() workaround is there now, but I hope there will be a
future patch that explains (and fixes) whatever made the value change
from underneath that code.

          Linus