From: patchwork-bot+netdevbpf@kernel•org
To: Yevhen Orlov <yevhen.orlov@plvision•eu>
Cc: netdev@vger•kernel.org, volodymyr.mytnyk@plvision•eu,
taras.chornyi@plvision•eu, mickeyr@marvell•com,
serhiy.pshyk@plvision•eu, maksym.glubokiy@plvision•eu,
j.vosburgh@gmail•com, vfalico@gmail•com, andy@greyhouse•net,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, linux-kernel@vger•kernel.org
Subject: Re: [PATCH net] net: bonding: fix use-after-free after 802.3ad slave unbind
Date: Thu, 30 Jun 2022 04:00:13 +0000 [thread overview]
Message-ID: <165656161371.1686.14484699232188262665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220629012914.361-1-yevhen.orlov@plvision.eu>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 29 Jun 2022 04:29:14 +0300 you wrote:
> commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection"),
> resolve case, when there is several aggregation groups in the same bond.
> bond_3ad_unbind_slave will invalidate (clear) aggregator when
> __agg_active_ports return zero. So, ad_clear_agg can be executed even, when
> num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for,
> previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave
> will not update slave ports list, because lag_ports==NULL. So, here we
> got slave ports, pointing to freed aggregator memory.
>
> [...]
Here is the summary with links:
- [net] net: bonding: fix use-after-free after 802.3ad slave unbind
https://git.kernel.org/netdev/net/c/050133e1aa2c
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:[~2022-06-30 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:29 [PATCH net] net: bonding: fix use-after-free after 802.3ad slave unbind Yevhen Orlov
2022-06-29 18:58 ` Jay Vosburgh
2022-06-30 4:00 ` 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=165656161371.1686.14484699232188262665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andy@greyhouse$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=j.vosburgh@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maksym.glubokiy@plvision$(echo .)eu \
--cc=mickeyr@marvell$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=serhiy.pshyk@plvision$(echo .)eu \
--cc=taras.chornyi@plvision$(echo .)eu \
--cc=vfalico@gmail$(echo .)com \
--cc=volodymyr.mytnyk@plvision$(echo .)eu \
--cc=yevhen.orlov@plvision$(echo .)eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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