From: patchwork-bot+netdevbpf@kernel.org
To: Kalpesh Solanki <skalpesh942@gmail.com>
Cc: jv@jvosburgh.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, socketcan@hartkopp.net,
yaojiale02@163.com
Subject: Re: [PATCH] bonding: reject IEEE 802.15.4 and 6LoWPAN devices in bond_enslave
Date: Tue, 17 Nov 2026 11:50:08 +0000 [thread overview]
Message-ID: <179491620877.531240.2226036750385717075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112130833.233208-1-skalpesh942@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 12 Nov 2026 18:38:33 +0530 you wrote:
> When the first non-Ethernet slave is enslaved to a bond,
> bond_setup_by_slave() copies slave_dev->type to the bond device.
> However, the bonding driver does not set up subsystem-specific
> mid-layer contexts or private structures:
>
> 1. IEEE 802.15.4 routines (such as ieee802154_llsec_dump_table(),
> nl-phy.c, and socket callbacks) identify WPAN devices by dev->type
> alone and unconditionally dereference dev->ieee802154_ptr and
> dev->ml_priv (ieee802154_mlme_ops). Because bonding never allocates
> these, this results in a NULL pointer dereference.
>
> [...]
Here is the summary with links:
- bonding: reject IEEE 802.15.4 and 6LoWPAN devices in bond_enslave
https://git.kernel.org/netdev/net/c/297ae1590173
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:[~2026-11-17 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 13:08 [PATCH] bonding: reject IEEE 802.15.4 and 6LoWPAN devices in bond_enslave Kalpesh Solanki
2026-11-12 13:10 ` netdev-bot+sinfo
2026-11-12 13:20 ` KALPESH SOLANKI
2026-11-12 13:32 ` Oliver Hartkopp
2026-11-13 2:44 ` Hangbin Liu
2026-11-17 11:50 ` 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=179491620877.531240.2226036750385717075.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=jv@jvosburgh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=skalpesh942@gmail.com \
--cc=socketcan@hartkopp.net \
--cc=yaojiale02@163.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