Hi Greg,
On 2025-08-26 13:02, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 6.6.103 release. There are 587 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 Thu, 28 Aug 2025 11:08:24 +0000. Anything received after that time might be too late.
Quick query - should we be backporting a known regression, even if it is in mainline presently, or do we wait until the fix is applied to mainline and *then* backport both patches?
9e30ecf23b1b ("net: ipv4: fix incorrect MTU in broadcast routes")
introduces a regression which breaks IPv4 broadcast, which stops WOL working (breaking my CI system), among other things:
https://lore.kernel.org/regressions/20250822165231.4353-4-bacs@librecast.net
This regression has *already* been backported to:
- 6.16.3 - 6.12.43
so I guess we wait for a fix for these.
However, it is not yet present in the other stable kernels. The new stable release candidates today would spread the breakage to:
- 6.6.y - 6.1.y - 5.15.y - 5.10.y
Do we revert this patch in today's RCs for now, or keep it for full compatibility with mainline bugliness?
Cheers,
Brett --