netdev - Re: [PATCH net 1/1] qlcnic: Delete existing multicast MAC list before adding new

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: <20150211.194334.1487182178426500477.davem@davemloft.net>
Date:	Wed, 11 Feb 2015 19:43:34 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	shahed.shaikh@...gic.com
Cc:	netdev@...r.kernel.org, Dept-GELinuxNICDev@...gic.com
Subject: Re: [PATCH net 1/1] qlcnic: Delete existing multicast MAC list
 before adding new

From: Shahed Shaikh <shahed.shaikh@...gic.com>
Date: Wed, 11 Feb 2015 09:45:24 -0500

> From: Shahed Shaikh <shahed.shaikh@...gic.com>
> 
> Driver keeps adding multicast addresses without deleting removed MACs and
> worrying about adapters filter limit. This results into actual count of programmed
> multicast addresses get accumulated over the time and overruns the adapter's
> filter limit without putting device in ACCEPT_ALL_MULTI mode. This causes
> newly added multicast traffic to fail after the sequence of addition - deletion
> in certain pattern.
> 
> This issue is seen only when netdev's mcast list count is less than adapters
> mcast filter limit.
> 
> e.g. If adapters multicast filter limit is 38 per function
>      then following sequence would result in multicast traffic failure for
>      newly added MACs.
>      - add less than 38 multicast MACs
>      - remove previously added multicast MACs
>      - add new multicast MACs (less than 38)
> 
> Signed-off-by: Shahed Shaikh <shahed.shaikh@...gic.com>

Applied.
--
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