From: patchwork-bot+netdevbpf@kernel.org
To: Tonghao Zhang <tonghao@bamaicloud.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net, andrew+netdev@lunn.ch,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
liuhangbin@gmail.com, razor@blackwall.org, vincent@bernat.ch,
stable@vger.kernel.org
Subject: Re: [PATCH net] net: bonding: fix possible peer notify event loss or dup issue
Date: Thu, 23 Oct 2025 11:20:05 +0000 [thread overview]
Message-ID: <176121840586.3001126.18409474218756623058.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251021050933.46412-1-tonghao@bamaicloud.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 21 Oct 2025 13:09:33 +0800 you wrote:
> If the send_peer_notif counter and the peer event notify are not synchronized.
> It may cause problems such as the loss or dup of peer notify event.
>
> Before this patch:
> - If should_notify_peers is true and the lock for send_peer_notif-- fails, peer
> event may be sent again in next mii_monitor loop, because should_notify_peers
> is still true.
> - If should_notify_peers is true and the lock for send_peer_notif-- succeeded,
> but the lock for peer event fails, the peer event will be lost.
>
> [...]
Here is the summary with links:
- [net] net: bonding: fix possible peer notify event loss or dup issue
https://git.kernel.org/netdev/net/c/10843e1492e4
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:[~2025-10-23 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 5:09 [PATCH net] net: bonding: fix possible peer notify event loss or dup issue Tonghao Zhang
2025-10-22 1:08 ` Jay Vosburgh
2025-10-23 11:20 ` 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=176121840586.3001126.18409474218756623058.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=stable@vger.kernel.org \
--cc=tonghao@bamaicloud.com \
--cc=vincent@bernat.ch \
/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;
as well as URLs for NNTP newsgroup(s).