netdev - Re: [PATCH 3.14-stable] 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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 1 Jun 2014 15:38:53 +0800
From:	Wei Yang <weiyang@...ux.vnet.ibm.com>
To:	Wei Yang <weiyang@...ux.vnet.ibm.com>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Amir Vadai <amirv@...lanox.com>,
	Jack Morgenstein <jackm@....mellanox.co.il>,
	Or Gerlitz <ogerlitz@...lanox.com>
Subject: Re: [PATCH 3.14-stable] net/mlx4_core: Preserve pci_dev_data after
 __mlx4_remove_one()

David,

Following are the backport of this patch to 3.14, 3.10, 3.4 and 3.2 stable
tree.

On 3.14, only this patch is backported.
On 3.10, a previous related one "pass pci_device_id.driver_data to
         __mlx4_init_one during reset" is backported too.
On 3.4,  "pass pci_device_id.driver_data to __mlx4_init_one during reset" is
         not backported, since the slot_reset handler is not presented.
	 While another one, "Stash PCI ID driver_data in mlx4_priv structure"
	 is backported to make this patch valid on this version.
On 3.2,  The same as 3.4.

All version are compiled successfully. 3.14 and 3.10 are verified, while 3.4
and 3.2 are not.

I am not sure how to make them all in one big patch set, so send them
seperatedly. Each version is contained in one patch set. If there is a better
way for you to merge them, please let me know.

At last, Happy Children's Day for all :-)

-- 
Richard Yang
Help you, Help me

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