linux-kernel - Re: [PATCH] PCI: connect struct pci_dev to struct pci

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, 23 Sep 2008 11:14:13 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Alex Chiang <achiang@...com>
Cc:	linux-pci <linux-pci@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] PCI: connect struct pci_dev to struct pci_slot

On Tuesday, September 2, 2008 8:40 am Alex Chiang wrote:
> The introduction of struct pci_slot (f46753c5e354b857b20ab8e0fe7b25)
> added a struct pci_slot pointer to struct pci_dev, but we forgot to
> associate the two.
>
> Connect the two structs together; the interesting portions of the object
> lifetimes are:
>
> 	- when a new pci_slot is created, connect it to the appropriate
> 	  pci_dev's. A single pci_slot may be associated with multiple
> 	  pci_dev's, e.g. any multi-function PCI device.
>
> 	- when a pci_slot is released, look for all the pci_dev's it was
> 	  associated with, and set their pci_slot pointers to NULL
>
> 	- when a pci_dev is created, look for slots to associate with.
>
> Note -- when a pci_dev is released, we don't need to do any bookkeeping,
> since pci_slot's do not have pointers to pci_dev's.
>
> Signed-off-by: Alex Chiang <achiang@...com>

Applied to linux-next.  Thanks.

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