From: David Miller <davem@davemloft.net>
To: jpirko@redhat.com
Cc: robert.w.love@intel.com, James.Bottomley@suse.de,
linux-scsi@vger.kernel.org, devel@open-fcoe.org,
netdev@vger.kernel.org, fubar@us.ibm.com, joe.eykholt@gmail.com
Subject: Re: fcoe: correct checking for bonding
Date: Sat, 12 Mar 2011 10:59:44 -0800 (PST) [thread overview]
Message-ID: <20110312.105944.193725929.davem@davemloft.net> (raw)
In-Reply-To: <20110312120109.GA2899@psychotron.redhat.com>
From: Jiri Pirko <jpirko@redhat.com>
Date: Sat, 12 Mar 2011 13:01:10 +0100
> Thu, Mar 03, 2011 at 02:09:18AM CET, robert.w.love@intel.com wrote:
>>On Wed, 2011-03-02 at 01:55 -0800, Jiri Pirko wrote:
>>> Or perhaps this should be applied to net-next?
>>>
>>I think this should go through scsi-misc as all the other
>>libfc/libfcoe/fcoe patches do.
>>
>>> Wed, Mar 02, 2011 at 07:05:35AM CET, jpirko@redhat.com wrote:
>>> >Check for bonding master and refuse to use that.
>>> >
>>> >Signed-off-by: Jiri Pirko <jpirko@redhat.com>
>>> >---
>>> > drivers/scsi/fcoe/fcoe.c | 4 +---
>>> > 1 files changed, 1 insertions(+), 3 deletions(-)
>>> >
>>> >diff --git a/drivers/scsi/fcoe/fcoe.c b/drivers/scsi/fcoe/fcoe.c
>>> >index 9f9600b..3becc6a 100644
>>> >--- a/drivers/scsi/fcoe/fcoe.c
>>> >+++ b/drivers/scsi/fcoe/fcoe.c
>>> >@@ -285,9 +285,7 @@ static int fcoe_interface_setup(struct fcoe_interface *fcoe,
>>> > }
>>> >
>>> > /* Do not support for bonding device */
>>> >- if ((netdev->priv_flags & IFF_MASTER_ALB) ||
>>> >- (netdev->priv_flags & IFF_SLAVE_INACTIVE) ||
>>> >- (netdev->priv_flags & IFF_MASTER_8023AD)) {
>>> >+ if (netdev->priv_flags & IFF_BONDING && netdev->flags & IFF_MASTER) {
>>> > FCOE_NETDEV_DBG(netdev, "Bonded interfaces not supported\n");
>>> > return -EOPNOTSUPP;
>>> > }
>>> >--
>>> >1.7.3.4
>>> >
>>
>>James, feel free to pick up this patch. I don't have anything in my fcoe
>>tree right now that it would conflict with. I'll also put it in my tree
>>and resend if you don't put it into scsi-misc directly.
>
> What's the status of this? Maybe this should rather go thru net-next
Sure, I can take this. I'll look at it later.
next prev parent reply other threads:[~2011-03-12 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 6:05 fcoe: correct checking for bonding Jiri Pirko
2011-03-02 9:55 ` Jiri Pirko
2011-03-03 1:09 ` Robert Love
2011-03-12 12:01 ` Jiri Pirko
2011-03-12 18:59 ` David Miller [this message]
2011-03-14 19:04 ` Robert Love
2011-03-14 19:22 ` Jiri Pirko
2011-03-14 20:20 ` David Miller
2011-03-14 20:53 ` James Bottomley
2011-03-14 21:04 ` 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=20110312.105944.193725929.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@suse.de \
--cc=devel@open-fcoe.org \
--cc=fubar@us.ibm.com \
--cc=joe.eykholt@gmail.com \
--cc=jpirko@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.w.love@intel.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;
as well as URLs for NNTP newsgroup(s).