On Thu, Jul 24, 2025 at 12:59:47PM +0200, Maciej Wieczor-Retman wrote:
As I wrote in the v2 thread, based on what's in the documentation added at the commit I pointed out, the behavior is a bug.
That's all missing the whole idea of Fixes: tags and backports.
Your patch must point to the correct faulty commit which causes this behavior or to none, which means backport everywhere. And I already explained this to you.
Pointing to a commit documenting this doesn't make the tree *before* that all of a sudden not affected.
What I would do is, I'd go through all stable trees and check whether they're affected. If they are, you craft backports for all of them. You were already asking Greg what to do.
But pointing to some innocuous commit and deciding that that is the culprit is not what you should do.
Thx.