linux-kernel - [PATCH 0/7] PCI: fix pci dev add and remove sequence

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-next>] [day] [month] [year] [list]

Message-Id: <1368498506-25857-1-git-send-email-yinghai@kernel.org>
Date:	Mon, 13 May 2013 19:28:19 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Gu Zheng <guz.fnst@...fujitsu.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>
Subject: [PATCH 0/7] PCI: fix pci dev add and remove sequence

The patchset is started while we try to address double remove pci
devices via sysfs that is found by Gu.

main point is from Bjorn that add reference for bus, and he also
pointed out that release should be done in pci_release_device.

After reviewing the add and remove path, found more problem that
need to be addressed, like
1. proc attach/detach is not balanced
2. stop_and_remove device is not multiple calling safe.

Also found sriov VFs add path has problem, it call pci_bus_add_device
to early, and it will make VF's driver get probed before PF's driver
probing is done. That will also have nested lock problem.

Please consider those patches to be 3.10 materials.

Thanks

Yinghai

  PCI: move back pci_proc_attach_devices calling
  PCI: move resources and bus_list releasing to pci_release_dev
  PCI: Detach driver in pci_stop_device
  PCI: Fix racing for pci device removing via sysfs
  PCI, ACPI: Don't glue ACPI dev with pci VFs
  PCI: Make sure VF's driver get attached after PF's
  PCI: use pf as dma_dev for vf that does not have func0 sibling
--
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/