From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Toppins <jtoppins@redhat.com>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, joamaki@gmail.com
Subject: Re: [PATCH net v2 0/2] bonding: fix NULL deref in bond_rr_gen_slave_id
Date: Thu, 22 Sep 2022 14:10:15 +0000 [thread overview]
Message-ID: <166385581598.2095.4389439130979294872.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1663694476.git.jtoppins@redhat.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Sep 2022 13:45:50 -0400 you wrote:
> Fix a NULL dereference of the struct bonding.rr_tx_counter member because
> if a bond is initially created with an initial mode != zero (Round Robin)
> the memory required for the counter is never created and when the mode is
> changed there is never any attempt to verify the memory is allocated upon
> switching modes.
>
> The first patch provides a selftest to demonstrate the issue and the
> second patch fixes the issue.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] selftests: bonding: cause oops in bond_rr_gen_slave_id
https://git.kernel.org/netdev/net/c/2ffd57327ff1
- [net,v2,2/2] bonding: fix NULL deref in bond_rr_gen_slave_id
https://git.kernel.org/netdev/net/c/0e400d602f46
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-09-22 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:45 [PATCH net v2 0/2] bonding: fix NULL deref in bond_rr_gen_slave_id Jonathan Toppins
2022-09-20 17:45 ` [PATCH net v2 1/2] selftests: bonding: cause oops " Jonathan Toppins
2022-09-20 17:45 ` [PATCH net v2 2/2] bonding: fix NULL deref " Jonathan Toppins
2022-09-20 17:53 ` [PATCH net v2 0/2] " Jay Vosburgh
2022-09-22 14:10 ` 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=166385581598.2095.4389439130979294872.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=j.vosburgh@gmail.com \
--cc=joamaki@gmail.com \
--cc=jtoppins@redhat.com \
--cc=netdev@vger.kernel.org \
/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).