Netdev List
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Jiri Pirko <jiri@resnulli.us>
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 16:12:18 +0200	[thread overview]
Message-ID: <20190412141218.GA29605@bistromath.localdomain> (raw)
In-Reply-To: <20190412135755.GA2268@nanopsycho.orion>

2019-04-12, 15:57:55 +0200, Jiri Pirko wrote:
> 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.

I don't have one, but nothing is preventing that setup. It's just
something I accidentally ran into while testing other things. If you
want to prevent bond-bond, you also need to prevent things like
bond-macvlan-bond for example. The set of rules of what types of
stacking make sense seems a bit hairy.

-- 
Sabrina

  reply	other threads:[~2019-04-12 14:12 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
2019-04-12 14:12   ` Sabrina Dubroca [this message]
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=20190412141218.GA29605@bistromath.localdomain \
    --to=sd@queasysnail.net \
    --cc=andy@greyhouse.net \
    --cc=j.vosburgh@gmail.com \
    --cc=jarod@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --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