On Tue, Feb 4, 2025 at 8:29 AM Chuck Lever via Bugspray Bot <bugbot@xxxxxxxxxx> wrote: > > Chuck Lever writes via Kernel.org Bugzilla: > > (In reply to rik.theys from comment #7) > > Is it possible this patch has not (yet) been sent to stable@xxxxxxxxxxxxxxx > > so it ends up in 6.12.y? > > Commit 1b3e26a5ccbf has been in a publicly released kernel for exactly two days (as of this writing). It will take some time before it appears in any LTS kernel. For now, if you would like to test the commit, you need to apply it manually. I believe there is something more to this problem. 1b3e26a5ccbf commit isn't sufficient. I also have report of "cb_status=-521 tk_status=-10036 cb_opcode=3" triggered warning. > > View: https://bugzilla.kernel.org/show_bug.cgi?id=219737#c8 > You can reply to this message to join the discussion. > -- > Deet-doot-dot, I am a bot. > Kernel.org Bugzilla (bugspray 0.1-dev) >
