On Wed, Mar 19, 2025 at 3:33 AM Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Caused by the resilient-queued-spin-lock branch of the bpf-next tree > interacting with the "Enable strict percpu address space checks" series > form the mm-stable tree. > > I don't know why this happens, but reverting that branch inf the bpf-next > tree makes the failure go away, so I have done that for today. percpu pointers are now checked by the compiler, and their address spaces have to be handled properly. It is like "sparse" rule, but now enforced by the compiler. This functionality was in fact introduced to catch programming errors like this. Thanks, Uros.
