linux-kernel - Re: [PATCH 3.10 26/52] net/mlx4_core: Preserve pci_dev_data after __mlx4_remove

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: <53AA6A94.7000104@mellanox.com>
Date:	Wed, 25 Jun 2014 09:22:12 +0300
From:	Or Gerlitz <ogerlitz@...lanox.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Wei Yang <weiyang@...ux.vnet.ibm.com>,
	"David S. Miller" <davem@...emloft.net>
CC:	<linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Amir Vadai <amirv@...lanox.com>,
	Jack Morgenstein <jackm@....mellanox.co.il>,
	Or Gerlitz <or.gerlitz@...il.com>
Subject: Re: [PATCH 3.10 26/52] net/mlx4_core: Preserve pci_dev_data after
 __mlx4_remove_one()

On 25/06/2014 09:02, Or Gerlitz wrote:
> On 24/06/2014 18:50, Greg Kroah-Hartman wrote:
>> 3.10-stable review patch.  If anyone has any objections, please let 
>> me know.
>>
>> ------------------
>>
>> From: Wei Yang <weiyang@...ux.vnet.ibm.com>
>>
>> [ Upstream commit befdf8978accecac2e0739e6b5075afc62db37fe ]
>
> Hi Wei, Dave,
>
> In the same manner you acted for 3.14.y -- for this commit to go into 
> 3.10.y it must be accompanied by commit 
> da1de8dfff09d33d4a5345762c21b487028e25f5  "net/mlx4_core: Keep only 
> one driver entry release mlx4_priv" which fixes a bug introduced by 
> the former, agree?
>
>
>
NAK, you're right... we only need the 2nd fix for kernels >= 3.14 which 
contain commit 367d56f "net/mlx4: Support shutdown() interface", before 
that -- it's irrelevant, sorry for the spam.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/