On 4/8/26 10:58, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.1.168 release. There are 312 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Fri, 10 Apr 2026 17:58:42 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at: https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.168-rc1... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y and the diffstat can be found below.
thanks,
greg k-h
Tested on an amd64 laptop (Lenovo ThinkPad T14 Gen 1). Working well, no regressions observed.
Tested-by: Barry K. Nathan barryn@pobox.com
However, I'm curious about what's happening with 6.1.y and the "CrackArmor" AppArmor fixes. As far as I can tell, they're still not in 6.1.168-rc1 (and presumably won't be in 6.1.168). Assuming it's not too early to talk about it in public yet, where does this stand? Is it just a matter of waiting a bit longer for stuff to happen behind the scenes (or for other bugs/patches to be dealt with first), or is there something else going on (such as a specific problem blocking it that needs to be resolved first)?