From: patchwork-bot+netdevbpf@kernel.org
To: Yufeng Mo <moyufeng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, jay.vosburgh@canonical.com,
jiri@resnulli.us, netdev@vger.kernel.org, nikolay@nvidia.com,
shenjian15@huawei.com, lipeng321@huawei.com,
yisen.zhuang@huawei.com, linyunsheng@huawei.com,
huangguangbin2@huawei.com, chenhao288@hisilicon.com,
salil.mehta@huawei.com, linuxarm@huawei.com,
linuxarm@openeuler.org
Subject: Re: [PATCH V2 net-next] bonding: 3ad: fix the concurrency between __bond_release_one() and bond_3ad_state_machine_handler()
Date: Mon, 02 Aug 2021 09:30:06 +0000 [thread overview]
Message-ID: <162789660658.5679.14400779141118515659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1627611551-33333-1-git-send-email-moyufeng@huawei.com>
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
prev parent reply other threads:[~2021-08-02 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 2:19 [PATCH V2 net-next] bonding: 3ad: fix the concurrency between __bond_release_one() and bond_3ad_state_machine_handler() Yufeng Mo
2021-08-02 9:30 ` 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=162789660658.5679.14400779141118515659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=linuxarm@openeuler.org \
--cc=linyunsheng@huawei.com \
--cc=lipeng321@huawei.com \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=yisen.zhuang@huawei.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;
as well as URLs for NNTP newsgroup(s).