[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54AA89F0.9090009@intel.com>
Date: Mon, 05 Jan 2015 12:56:16 +0000
From: Hubert Sokolowski <hubert.sokolowski@...el.com>
To: Roopa Prabhu <roopa@...ulusnetworks.com>
CC: Jamal Hadi Salim <jhs@...atatu.com>, vyasevic@...hat.com,
John Fastabend <john.fastabend@...il.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next RESEND] net: Do not call ndo_dflt_fdb_dump if
ndo_fdb_dump is defined.
On 19/12/14 16:32, Roopa Prabhu wrote:
> On 12/19/14, 7:17 AM, Hubert Sokolowski wrote:
>> On 18/12/14 22:32, Jamal Hadi Salim wrote:
>>
>>> Sorry for the latency (head-buried-in-sand in effect)
>>> On 12/17/14 11:18, Hubert Sokolowski wrote:
>>>> I have just prepared a patch where I dump uc/mc for bridge devices
>>>> by looking at (dev->priv_flags & IFF_EBRIDGE), so I have same results
>>>> as without my changes. This should satisfy Jamal and Roopa.
>>>> I could send it as v3 of my patch along with the results if you are
>>>> interested.
>>> Please do. If you satisfy Vlad's goals then we are all happy.
>> Posted as v3, please review.
>> There is still open question I asked sometime ago but never got explained.
>> It is about the new filter_dev parameter that was added to ndo_fdb_dump:
>> int (*ndo_fdb_dump)(struct sk_buff *skb,
>> struct netlink_callback *cb,
>> struct net_device *dev,
>> struct net_device *filter_dev,
>> int idx);
>>
>> When we call this function for a device, dev pointer is passed as the filter_dev:
>> if (dev->netdev_ops->ndo_fdb_dump)
>> idx = dev->netdev_ops->ndo_fdb_dump(skb, cb, bdev, dev,
>> idx);
> seems like these calls should be fixed. bdev is really dev in this case. And filter_dev should be null.
>
Will fix this too and resend the patch as v4.
Thanks,
Hubert
--
Hubert Sokolowski Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists