netdev - Re: [PATCH 0/5] 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]

Date:	Tue, 13 Oct 2015 04:33:09 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sathya.perla@...gotech.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 0/5] be2net: patch set

From: Sathya Perla <sathya.perla@...gotech.com>
Date: Mon, 12 Oct 2015 03:47:16 -0400

> Patch 1 fixes a FW image compatibility check in the driver that
> prevents certain FW images from being flashed on BE3 (not BE3-R)
> adapters.
> 
> Patch 2 fixes a spin_lock not being released in a failure case in
> be_cmd_notify_wait().
> 
> Patch 3 includes a workaround to pad packets that are only 32b long or less
> to be applicabe to BE3 too. This workaround was currently applied only to
> Skyhawk and Lancer chips. Such packets are causing BE3's TX path to stall
> on a SR-IOV config.
> 
> Patch 4 fixes the be_cmd_get_profile_config() routine to set the pf_num
> field in the cmd request. The FW requires this field to be set for it to
> return the specific function's descriptors. If not set, the FW returns
> the descriptors of all the functions on the device. If the first descriptor
> is not what is being queried for, the driver will read wrong data.
> This patch fixes this issue by using the GET_CNTL_ATTRIB cmd to query the
> real pci_func_num of a function and then uses it in the GET_PROFILE_CONFIG
> cmd.
> 
> Patch 5 completes an earlier fix that removed the vlan promisc capability
> for VFs. The earlier fix did not update the removal of this capability from
> the profile descriptor of the VF. This causes the VF driver to request this
> capability when it tries to create it's interface at probe time. This could
> potentailly cause the VF probe to fail if the FW enforces strict checking of
> the flags based on what was provisoned by the PF.  This strict checking is
> not being done by FW currently but will be fixed in a future version. This
> patch fixes this issue by updating the VF's profile descriptor so that they
> match the interface capability flags provisioned by the PF.
> 
> Pls consider adding these patches to the net tree. Thanks!

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