Subject: Re: [PATCH net-next v3 0/4] net: hsr: address functional and concurrency bugs

From: Jakub Kicinski <[email-masked]>
Date: Tue, 31 Mar 2026 19:37:58 -0700

On Sun, 29 Mar 2026 13:23:09 +0200 [email-masked] wrote:
> This series addresses four logic bugs in the HSR/PRP implementation 
> identified during a protocol audit.
> 
> The primary change resolves a race condition in the node merging path by
> implementing address-based lock ordering. This ensures that concurrent
> mutations of sequence blocks do not lead to state corruption or  
> deadlocks.
> 
> Additional fixes include correcting asymmetric VLAN error unwinding,
> enforcing strict supervision frame TLV validation, and improving Netlink
> error reporting for invalid interlink attributes.

I think that patches 1 and 2 need to go to net with a Fixes tag.
They look like run of the mill bug fixes. 3 and 4 are logical
fixes and change behavior so net-next makes sense.

FWIW AI has something to say about patch 3, I did not investigate:
https://sashiko.dev/#/patchset/[email-masked]
-- 
pw-bot: cr