From: Veaceslav Falico <vfalico@gmail.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
netdev@vger.kernel.org, j.vosburgh@gmail.com,
gospo@cumulusnetworks.com, clsoto@linux.vnet.ibm.com,
davem@davemloft.net
Subject: Re: [PATCH net] bonding: fix destruction of bond with devices different from arphrd_ether
Date: Thu, 16 Jul 2015 08:14:31 +0200 [thread overview]
Message-ID: <20150716061431.GA19448@vps.falico.eu> (raw)
In-Reply-To: <55A6E48E.3020206@cumulusnetworks.com>
On Thu, Jul 16, 2015 at 12:54:06AM +0200, Nikolay Aleksandrov wrote:
...snip...
>My personal opinion would be to disable non-ethernet devices, but support was
>already added and has been there for a long time so we have to fix this for
>the older releases, I don't mind removing non-ethernet device support for net-next
>but I'm guessing there're people still using that like the case that started
>this thread.
Yep, last time non-ethernet devices broke there were quite a few reports
for ppp users, and infiniband is indeed used a lot too. No options here, we
must support it...
next prev parent reply other threads:[~2015-07-16 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 18:57 [PATCH] net/bonding: Add function bond_remove_proc_entry at __bond_release_one clsoto
2015-07-13 21:05 ` Nikolay Aleksandrov
2015-07-13 21:10 ` Nikolay Aleksandrov
2015-07-15 17:49 ` Nikolay Aleksandrov
2015-07-15 19:52 ` [PATCH net] bonding: fix destruction of bond with devices different from arphrd_ether Nikolay Aleksandrov
2015-07-15 21:01 ` Carol Soto
2015-07-15 22:39 ` Eric W. Biederman
2015-07-15 22:54 ` Nikolay Aleksandrov
2015-07-15 22:58 ` Carol Soto
2015-07-16 6:14 ` Veaceslav Falico [this message]
2015-07-20 19:56 ` 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=20150716061431.GA19448@vps.falico.eu \
--to=vfalico@gmail.com \
--cc=clsoto@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=razor@blackwall.org \
/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;
as well as URLs for NNTP newsgroup(s).