netdev - Re: [PATCH 0/3] be2net: patch set

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: <20150807.115758.661898041262862547.davem@davemloft.net>
Date:	Fri, 07 Aug 2015 11:57:58 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sathya.perla@...gotech.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 0/3] be2net: patch set

From: Sathya Perla <sathya.perla@...gotech.com>
Date: Wed,  5 Aug 2015 03:27:47 -0400

> This patch set contains 2 driver fixes to a Lancer HW issue and a fix
> to a double free bug. Pls apply to the "net" tree. Thanks!
> 
> Patch 1 now enables filters only after creating RXQs. This is done as 
> HW issues were observed on Lancer adapters if filters
> (flags, mac addrs etc) are enabled *before* creating RXQs. This patch
> changes the driver design by enabling filters in be_open() --
> instead of be_setup() -- after RXQs are created and buffers posted.
> 
> Patch 2 fixes an RX stall issue that was seen on Lancer adapters when
> RXQs are destroyed while they are in an "out of buffer" state.
> This patch fixes this issue by posting 64 buffers to each RXQ before
> destroying them in the close path. This is done after ensuring that no
> more new packets are selected for transfer to the RXQs by disabling
> interface filters.
> 
> Patch 3 protects eqo->affinity_mask variable from being freed twice and
> resulting in a crash.  It's now freed only when EQs haven't yet been
> destroyed.

Series applied, thanks.
--
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