From: patchwork-bot+netdevbpf@kernel.org
To: Luka Gejak <luka.gejak@linux.dev>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, fmaurer@redhat.com,
horms@kernel.org, bigeasy@linutronix.de, m-karicheri2@ti.com
Subject: Re: [PATCH net v4 0/2] net: hsr: fixes for PRP duplication and VLAN unwind
Date: Thu, 02 Apr 2026 15:40:10 +0000 [thread overview]
Message-ID: <177514441079.499423.6384595967284377573.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401092243.52121-1-luka.gejak@linux.dev>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 1 Apr 2026 11:22:41 +0200 you wrote:
> From: Luka Gejak <luka.gejak@linux.dev>
>
> This series addresses two logic bugs in the HSR/PRP implementation
> identified during a protocol audit. These are targeted for the 'net'
> tree as they fix potential memory corruption and state inconsistency.
>
> 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.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] net: hsr: serialize seq_blocks merge across nodes
https://git.kernel.org/netdev/net/c/f5df2990c364
- [net,v4,2/2] net: hsr: fix VLAN add unwind on slave errors
https://git.kernel.org/netdev/net/c/2e3514e63bfb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-02 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 9:22 [PATCH net v4 0/2] net: hsr: fixes for PRP duplication and VLAN unwind luka.gejak
2026-04-01 9:22 ` [PATCH net v4 1/2] net: hsr: serialize seq_blocks merge across nodes luka.gejak
2026-04-01 9:22 ` [PATCH net v4 2/2] net: hsr: fix VLAN add unwind on slave errors luka.gejak
2026-04-02 15:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177514441079.499423.6384595967284377573.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=luka.gejak@linux.dev \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox