[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162789660658.5679.14400779141118515659.git-patchwork-notify@kernel.org>
Date: Mon, 02 Aug 2021 09:30:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Yufeng Mo <moyufeng@...wei.com>
Cc: davem@...emloft.net, kuba@...nel.org, jay.vosburgh@...onical.com,
jiri@...nulli.us, netdev@...r.kernel.org, nikolay@...dia.com,
shenjian15@...wei.com, lipeng321@...wei.com,
yisen.zhuang@...wei.com, linyunsheng@...wei.com,
huangguangbin2@...wei.com, chenhao288@...ilicon.com,
salil.mehta@...wei.com, linuxarm@...wei.com, linuxarm@...neuler.org
Subject: Re: [PATCH V2 net-next] bonding: 3ad: fix the concurrency between
__bond_release_one() and bond_3ad_state_machine_handler()
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 30 Jul 2021 10:19:11 +0800 you wrote:
> Some time ago, I reported a calltrace issue
> "did not find a suitable aggregator", please see[1].
> After a period of analysis and reproduction, I find
> that this problem is caused by concurrency.
>
> Before the problem occurs, the bond structure is like follows:
>
> [...]
Here is the summary with links:
- [V2,net-next] bonding: 3ad: fix the concurrency between __bond_release_one() and bond_3ad_state_machine_handler()
https://git.kernel.org/netdev/net-next/c/220ade77452c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists