netdev - Re: bnx2x multicast packet loss on igmp join/leave

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABVbdp8qoUWhoUFDvVo-4pSkbGrGCYaqxhJPB6hDAW2_1B_CKw@mail.gmail.com>
Date:	Fri, 5 Apr 2013 15:06:48 +0200
From:	vincent Richard <vincent.richard449@...il.com>
To:	Dmitry Kravkov <dkravkov@...il.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: bnx2x multicast packet loss on igmp join/leave

2013/4/5, Dmitry Kravkov <dkravkov@...il.com>:
> On Fri, Apr 5, 2013 at 1:13 PM, vincent Richard
> <vincent.richard449@...il.com> wrote:
>>
>> I all,
>>
>> I am using a HP server with bnx2x ethernet cards in it.
>> I have compiled the latest linux 3.2 version, and I am encountering
>> the following error :
>>
>> when joining or leaving a multicast group, other multicast streams
>> lose some packets.
>>
>> I tried latest firmware and different drivers (latest HP recommended
>> one (redhat one)) but still the same..
>>
>> I observe that putting the interface in promiscuous mode make the
>> problem disappear.
>>
>> looking around bnx2x_set_rx_mode, i notice that there is 3 rx_mode,
>> NORMAL, PROMISCUOUS and ALLMULTI . forcing other than normal mode
>> correct my issue..
>>
>> My bnx2x is in a blade center so there is a switch just after. So
>> forcing PROMISCUOUS or ALLMULTI mode have no major impact.
>>
>> To reproduce the problem I just "listen" 2 multicast streams and
>> join/leave another one periodically.
>>
>> Thanks in advance for your help.
>> Regards,
>> Vincent
>
> This because on MC group change, bnx2x first removes the devices from
> ALL MC groups and then
> add the device to newly configured groups:
>
> 11112        /* first, clear all configured multicast MACs */
> 11113        rc = bnx2x_config_mcast(bp, &rparam, BNX2X_MCAST_CMD_DEL);
> 11114        if (rc < 0) {
> 11115                BNX2X_ERR("Failed to clear multicast
> configuration: %d\n", rc);
> 11116                return rc;
> 11117        }
> 11118
> 11119        /* then, configure a new MACs list */
> 11120        if (netdev_mc_count(dev)) {
> 11121               rc = bnx2x_init_mcast_macs_list(bp, &rparam);
>


Thanks for the quick answer, BTW I am very surprised of this behavior.
It is the first time I encounter (or see) this.
--
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