On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@xxxxxxxxxx> 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