From: David Gibson <dgibson@redhat.com>
To: "Christian Benvenuti (benve)" <benve@cisco.com>
Cc: David Miller <davem@davemloft.net>,
"gregory.v.rose@intel.com" <gregory.v.rose@intel.com>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Sujith Sankar (ssujith)" <ssujith@cisco.com>,
"govindarajulu90@gmail.com" <govindarajulu90@gmail.com>,
"Neel Patel (neepatel)" <neepatel@cisco.com>,
"nistrive@cisco.com" <nistrive@cisco.com>
Subject: Re: RFC: rtnetlink problems with Cisco enic and VFs
Date: Wed, 23 Apr 2014 14:15:51 +1000 [thread overview]
Message-ID: <20140423141551.e969a8a45bd494e468d56b09@redhat.com> (raw)
In-Reply-To: <6CE81A2095B0024BBC77007BD04E553823E87A41@xmb-aln-x02.cisco.com>
[-- Attachment #1: Type: text/plain, Size: 2837 bytes --]
On Wed, 23 Apr 2014 02:33:06 +0000
"Christian Benvenuti (benve)" <benve@cisco.com> wrote:
> > -----Original Message-----
> > From: netdev-owner@vger.kernel.org [mailto:netdev-
> > owner@vger.kernel.org] On Behalf Of David Miller
> > Sent: Tuesday, April 22, 2014 6:17 PM
> > To: dgibson@redhat.com
> > Cc: gregory.v.rose@intel.com; ben@decadent.org.uk;
> > netdev@vger.kernel.org; Christian Benvenuti (benve); Sujith Sankar
> > (ssujith); govindarajulu90@gmail.com; Neel Patel (neepatel);
> > nistrive@cisco.com
> > Subject: Re: RFC: rtnetlink problems with Cisco enic and VFs
> >
> > From: David Gibson <dgibson@redhat.com>
> > Date: Wed, 23 Apr 2014 11:12:03 +1000
> >
> > > And therein lies the problem. I don't even know what the
> > > IFLA_VF_PORTS info is for, but presumably something uses it. If they
> > > stop receiving it, they can be expected to break horribly.
>
> In the case of Enic, libvirt uses IFLA_VF_PORTS in the context of the port profile
> (see virtualport section and 802.1Qbh in the libvirt network xml documentation).
>
> As Miller said, libvirt and iproute2 are the two known users (with libvirt being the main one)
> but you never know what else may be using it.
Ah, yes, I see it in libvirt.
I don't think it's used in iproute2 though, at least not in the master
branch.
$ git remote show origin
* remote origin
Fetch URL:
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
Push URL:
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
HEAD branch: master Remote branches: iproute-3.5.1 tracked
master tracked
net-next tracked
net-next-3.11 tracked
net-next-for-3.13 tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)
$ git rev-parse HEAD
ce3436ca05ee2a9f4bf4c5b10eb25638865772cb
$ git grep IFLA_VF_PORTS
include/linux/if_link.h: IFLA_VF_PORTS,
include/linux/if_link.h: * [IFLA_VF_PORTS]
Those are declaration and comment only, no actual uses.
> > We did the same thing to VFINFO list.
>
> I guess you refer to Bugzilla 889319.
>
> > All the users I could find already set the mask unconditionally for all device
> > dumps.
> >
> > It's absolutely, positively, the only reasonable fix for this problem.
>
> The fix based on IFLA_EXT_MASK seems reasonable to me
> (IFLA_EXT_MASK is in use in libvirt >= 1.0.3 and iproute2 >=3.4.0 based on a quick check).
Ok. And conveniently for me it looks like the EXT_MASK fix is also
backported into the RHEL libvirt.
Alright, I'll whip up a patch series that makes the IFLA_VF_PORTS
information conditional on the RTEXT_FILTER_VF flag.
--
David Gibson <dgibson@redhat.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-23 4:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 4:14 RFC: rtnetlink problems with Cisco enic and VFs David Gibson
2014-04-22 4:17 ` David Gibson
2014-04-22 18:03 ` Ben Hutchings
2014-04-22 18:12 ` David Miller
2014-04-22 23:26 ` David Gibson
2014-04-23 0:04 ` Greg Rose
2014-04-23 1:12 ` David Gibson
2014-04-23 1:16 ` David Miller
2014-04-23 2:33 ` Christian Benvenuti (benve)
2014-04-23 4:15 ` David Gibson [this message]
2014-04-23 0:59 ` David Miller
2014-04-22 19:14 ` Christian Benvenuti (benve)
2014-04-22 23:24 ` David Gibson
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=20140423141551.e969a8a45bd494e468d56b09@redhat.com \
--to=dgibson@redhat.com \
--cc=ben@decadent.org.uk \
--cc=benve@cisco.com \
--cc=davem@davemloft.net \
--cc=govindarajulu90@gmail.com \
--cc=gregory.v.rose@intel.com \
--cc=neepatel@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=nistrive@cisco.com \
--cc=ssujith@cisco.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).