From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
j.vosburgh@gmail.com, andy@greyhouse.net, netdev@vger.kernel.org,
eric.dumazet@gmail.com, syzkaller@googlegroups.com
Subject: Re: [PATCH net] bonding: stop the device in bond_setup_by_slave()
Date: Tue, 14 Nov 2023 05:00:25 +0000 [thread overview]
Message-ID: <169993802509.31854.16280617174199384750.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231109180102.4085183-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 Nov 2023 18:01:02 +0000 you wrote:
> Commit 9eed321cde22 ("net: lapbether: only support ethernet devices")
> has been able to keep syzbot away from net/lapb, until today.
>
> In the following splat [1], the issue is that a lapbether device has
> been created on a bonding device without members. Then adding a non
> ARPHRD_ETHER member forced the bonding master to change its type.
>
> [...]
Here is the summary with links:
- [net] bonding: stop the device in bond_setup_by_slave()
https://git.kernel.org/netdev/net/c/3cffa2ddc4d3
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:[~2023-11-14 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 18:01 [PATCH net] bonding: stop the device in bond_setup_by_slave() Eric Dumazet
2023-11-09 20:26 ` Jay Vosburgh
2023-11-10 3:44 ` Hangbin Liu
2023-11-10 8:38 ` Eric Dumazet
2023-11-11 6:28 ` Hangbin Liu
2023-11-10 9:19 ` Jay Vosburgh
2023-11-11 6:34 ` Hangbin Liu
2023-11-14 0:43 ` Jay Vosburgh
2023-11-14 1:30 ` Hangbin Liu
2023-11-14 5: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=169993802509.31854.16280617174199384750.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller@googlegroups.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).