From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org,
syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com,
syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jann Horn <jannh@google.com>
Subject: Re: [Patch net v2] net: fix a potential recursive NETDEV_FEAT_CHANGE
Date: Wed, 06 May 2020 13:49:41 -0700 [thread overview]
Message-ID: <10173.1588798181@famine> (raw)
In-Reply-To: <20200506194613.18342-1-xiyou.wangcong@gmail.com>
Cong Wang <xiyou.wangcong@gmail.com> wrote:
>syzbot managed to trigger a recursive NETDEV_FEAT_CHANGE event
>between bonding master and slave. I managed to find a reproducer
>for this:
>
> ip li set bond0 up
> ifenslave bond0 eth0
> brctl addbr br0
> ethtool -K eth0 lro off
> brctl addif br0 bond0
> ip li set br0 up
>
>When a NETDEV_FEAT_CHANGE event is triggered on a bonding slave,
>it captures this and calls bond_compute_features() to fixup its
>master's and other slaves' features. However, when syncing with
>its lower devices by netdev_sync_lower_features() this event is
>triggered again on slaves when the LRO feature fails to change,
>so it goes back and forth recursively until the kernel stack is
>exhausted.
>
>Commit 17b85d29e82c intentionally lets __netdev_update_features()
>return -1 for such a failure case, so we have to just rely on
>the existing check inside netdev_sync_lower_features() and skip
>NETDEV_FEAT_CHANGE event only for this specific failure case.
>
>Fixes: 17b85d29e82c ("net/core: revert "net: fix __netdev_update_features return.." and add comment")
>Reported-by: syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com
>Reported-by: syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com
>Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>Cc: Josh Poimboeuf <jpoimboe@redhat.com>
>Cc: Jay Vosburgh <j.vosburgh@gmail.com>
>Cc: Jann Horn <jannh@google.com>
>Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Reviewed-by: Jay Vosburgh <jay.vosburgh@canonical.com>
>---
> net/core/dev.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>diff --git a/net/core/dev.c b/net/core/dev.c
>index 522288177bbd..6d327b7aa813 100644
>--- a/net/core/dev.c
>+++ b/net/core/dev.c
>@@ -8907,11 +8907,13 @@ static void netdev_sync_lower_features(struct net_device *upper,
> netdev_dbg(upper, "Disabling feature %pNF on lower dev %s.\n",
> &feature, lower->name);
> lower->wanted_features &= ~feature;
>- netdev_update_features(lower);
>+ __netdev_update_features(lower);
>
> if (unlikely(lower->features & feature))
> netdev_WARN(upper, "failed to disable %pNF on %s!\n",
> &feature, lower->name);
>+ else
>+ netdev_features_change(lower);
> }
> }
> }
>--
>2.26.2
>
prev parent reply other threads:[~2020-05-06 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 19:46 [Patch net v2] net: fix a potential recursive NETDEV_FEAT_CHANGE Cong Wang
2020-05-06 20:31 ` Nikolay Aleksandrov
2020-05-07 18:45 ` Cong Wang
2020-05-07 18:50 ` Nikolay Aleksandrov
2020-05-06 20:49 ` Jay Vosburgh [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=10173.1588798181@famine \
--to=jay.vosburgh@canonical.com \
--cc=jannh@google.com \
--cc=jpoimboe@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com \
--cc=syzbot+e73ceacfd8560cc8a3ca@syzkaller.appspotmail.com \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.