Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
	Veaceslav Falico <vfalico@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Jarod Wilson <jarod@redhat.com>
Subject: Re: [PATCH net] bonding: fix event handling for stacked bonds
Date: Fri, 12 Apr 2019 15:57:55 +0200	[thread overview]
Message-ID: <20190412135755.GA2268@nanopsycho.orion> (raw)
In-Reply-To: <9e7fda25884e8e68b1932a48de58189a08ef906f.1555073754.git.sd@queasysnail.net>

Fri, Apr 12, 2019 at 03:04:10PM CEST, sd@queasysnail.net wrote:
>When a bond is enslaved to another bond, bond_netdev_event() only
>handles the event as if the bond is a master, and skips treating the
>bond as a slave.
>
>This leads to a refcount leak on the slave, since we don't remove the
>adjacency to its master and the master holds a reference on the slave.
>
>Reproducer:
>  ip link add bondL type bond
>  ip link add bondU type bond
>  ip link set bondL master bondU
>  ip link del bondL

Out of curiosity, what is a usecase of stacked bonds? I don't see any.


>
>No "Fixes:" tag, this code is older than git history.
>
>Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
>---
>I also spotted some lockdep warnings when I started stacking random
>devices on top of random devices, I'm trying to clean that up too, but
>this fix is independent of that.
>
> drivers/net/bonding/bond_main.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index b59708c35faf..ee610721098e 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -3213,8 +3213,12 @@ static int bond_netdev_event(struct notifier_block *this,
> 		return NOTIFY_DONE;
> 
> 	if (event_dev->flags & IFF_MASTER) {
>+		int ret;
>+
> 		netdev_dbg(event_dev, "IFF_MASTER\n");
>-		return bond_master_netdev_event(event, event_dev);
>+		ret = bond_master_netdev_event(event, event_dev);
>+		if (ret != NOTIFY_DONE)
>+			return ret;
> 	}
> 
> 	if (event_dev->flags & IFF_SLAVE) {
>-- 
>2.21.0
>

  reply	other threads:[~2019-04-12 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 13:04 [PATCH net] bonding: fix event handling for stacked bonds Sabrina Dubroca
2019-04-12 13:57 ` Jiri Pirko [this message]
2019-04-12 14:12   ` Sabrina Dubroca
2019-04-15 20:23 ` David Miller

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=20190412135755.GA2268@nanopsycho.orion \
    --to=jiri@resnulli.us \
    --cc=andy@greyhouse.net \
    --cc=j.vosburgh@gmail.com \
    --cc=jarod@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=vfalico@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox