On Sat, May 30, 2026 at 4:36 AM Alexei Starovoitov <[email protected]> wrote: > I bet you fixed your android setup long ago, > so all of these "but what about backward compat" is getting annoying. > Whatever kernel patch get merged android won't even backport, so enough of it.
That’s partially correct, Android GKI does stick closely to upstream and mandates an upstream-first policy by default. However, we merged this specific kernel patch into the Android GKI 6.18 branch as an emergency fix, because internally we determined this is a kernel regression (introduced in commit 120933984460) rather than a userspace issue. So only kernel fix is merged, all the userspace program is untouched. We want to avoid carrying out-of-tree patches forward into next-generation Android kernel releases. That is why we are raising this here: we want to align on an upstream acceptable strategy to fix this issue so we don't carry a permanent fork or risk regression on future rebases. > Replied earlier that I don't like random checks like this through the code. Acked, I will raise a v2 patch to add theck in bpf_prog_query.
