From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: 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
Subject: Re: [PATCH net 0/2] bonding: properly restore flags when non-eth dev enslave fails
Date: Mon, 13 Mar 2023 15:42:01 +0200 [thread overview]
Message-ID: <e87c9c3d-2235-7800-e1ce-8495efdc0284@blackwall.org> (raw)
In-Reply-To: <20230313132834.946360-1-razor@blackwall.org>
On 13/03/2023 15:28, 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. Patch 01 fixes the bug and patch 02 adds a selftest for
> bond flags restoration in such cases. For more information please see
> commit descriptions.
>
> Thanks,
> Nik
>
> [1] https://syzkaller.appspot.com/bug?id=391c7b1f6522182899efba27d891f1743e8eb3ef
>
> Nikolay Aleksandrov (2):
> bonding: restore bond's IFF_SLAVE flag if a non-eth dev
> enslave fails
> selftests: rtnetlink: add a bond test trying to enslave non-eth dev
>
> drivers/net/bonding/bond_main.c | 8 +++++-
> tools/testing/selftests/net/rtnetlink.sh | 36 ++++++++++++++++++++++++
> 2 files changed, 43 insertions(+), 1 deletion(-)
>
Self-NAK, apologies for the noise. I'll send a v2 with the selftest adjusted to
always to attempt a cleanup after printing the errors regardless if the system hangs.
prev parent reply other threads:[~2023-03-13 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 13:28 [PATCH net 0/2] bonding: properly restore flags when non-eth dev enslave fails Nikolay Aleksandrov
2023-03-13 13:28 ` [PATCH net 1/2] bonding: restore bond's IFF_SLAVE flag if a " Nikolay Aleksandrov
2023-03-13 13:28 ` [PATCH net 2/2] selftests: rtnetlink: add a bond test trying to enslave non-eth dev Nikolay Aleksandrov
2023-03-13 13:32 ` Nikolay Aleksandrov
2023-03-13 13:34 ` Nikolay Aleksandrov
2023-03-13 13:42 ` Nikolay Aleksandrov [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=e87c9c3d-2235-7800-e1ce-8495efdc0284@blackwall.org \
--to=razor@blackwall.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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