From: Jonathan Toppins <jtoppins@redhat.com>
To: Nikolay Aleksandrov <razor@blackwall.org>, netdev@vger.kernel.org
Cc: monis@voltaire.com, syoshida@redhat.com, j.vosburgh@gmail.com,
andy@greyhouse.net, kuba@kernel.org, davem@davemloft.net,
pabeni@redhat.com, edumazet@google.com,
syzbot+9dfc3f3348729cc82277@syzkaller.appspotmail.com,
michal.kubiak@intel.com
Subject: Re: [PATCH net v3 0/3] bonding: properly restore flags when bond changes ether type
Date: Wed, 15 Mar 2023 10:44:26 -0400 [thread overview]
Message-ID: <0cfd57e7-2993-1bba-1918-022fe0e70930@redhat.com> (raw)
In-Reply-To: <20230315111842.1589296-1-razor@blackwall.org>
On 3/15/23 07:18, Nikolay Aleksandrov wrote:
> Hi,
> A bug was reported by syzbot[1] that causes a warning and a myriad of
> other potential issues if a bond, that is also a slave, fails to enslave a
> non-eth device. While fixing that bug I found that we have the same
> issues when such enslave passes and after that the bond changes back to
> ARPHRD_ETHER (again due to ether_setup). This set fixes all issues by
> extracting the ether_setup() sequence in a helper which does the right
> thing about bond flags when it needs to change back to ARPHRD_ETHER. It
> also adds selftests for these cases.
>
> Patch 01 adds the new bond_ether_setup helper and fixes the issues when a
> bond device changes its ether type due to successful enslave. Patch 02
> fixes the issues when it changes its ether type due to an unsuccessful
> enslave. Note we need two patches because the bugs were introduced by
> different commits. Patch 03 adds the new selftests.
>
> Due to the comment adjustment and squash, could you please review
> patch 01 again? I've kept the other acks since there were no code
> changes.
>
> v3: squash the helper patch and the first fix, adjust the comment above
> it to be explicit about the bond device, no code changes
> v2: new set, all patches are new due to new approach of fixing these bugs
>
> Thanks,
> Nik
>
> [1] https://syzkaller.appspot.com/bug?id=391c7b1f6522182899efba27d891f1743e8eb3ef
>
> Nikolay Aleksandrov (3):
> bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type
> change
> bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails
> selftests: bonding: add tests for ether type changes
>
> drivers/net/bonding/bond_main.c | 23 +++--
> .../selftests/drivers/net/bonding/Makefile | 3 +-
> .../net/bonding/bond-eth-type-change.sh | 85 +++++++++++++++++++
> 3 files changed, 103 insertions(+), 8 deletions(-)
> create mode 100755 tools/testing/selftests/drivers/net/bonding/bond-eth-type-change.sh
>
For the series.
Acked-by: Jonathan Toppins <jtoppins@redhat.com>
next prev parent reply other threads:[~2023-03-15 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 11:18 [PATCH net v3 0/3] bonding: properly restore flags when bond changes ether type Nikolay Aleksandrov
2023-03-15 11:18 ` [PATCH net v3 1/3] bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type change Nikolay Aleksandrov
2023-03-15 11:18 ` [PATCH net v3 2/3] bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails Nikolay Aleksandrov
2023-03-15 11:18 ` [PATCH net v3 3/3] selftests: bonding: add tests for ether type changes Nikolay Aleksandrov
2023-03-15 14:44 ` Jonathan Toppins [this message]
2023-03-15 14:57 ` [PATCH net v3 0/3] bonding: properly restore flags when bond changes ether type Michal Kubiak
2023-03-17 8:00 ` patchwork-bot+netdevbpf
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=0cfd57e7-2993-1bba-1918-022fe0e70930@redhat.com \
--to=jtoppins@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=michal.kubiak@intel.com \
--cc=monis@voltaire.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=syoshida@redhat.com \
--cc=syzbot+9dfc3f3348729cc82277@syzkaller.appspotmail.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