From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pz0-f46.google.com ([209.85.210.46]:40391 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759477Ab2HXOao (ORCPT ); Fri, 24 Aug 2012 10:30:44 -0400 Message-ID: <50379008.3080500@gmail.com> Date: Fri, 24 Aug 2012 22:30:32 +0800 From: Jiang Liu MIME-Version: 1.0 To: Liu ping fan CC: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Scott Murray , Bjorn Helgaas Subject: Re: pci: question about the life cycle of pci_dev and its parent pci_bus References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Sender: linux-pci-owner@vger.kernel.org List-ID: Hi Pingfan, We have realized the same when implementing lock mechanisms for PCI hotplug operations, and we are planning to holding a reference to parent bus for each pci dev. Regards! Gerry On 08/23/2012 01:24 PM, Liu ping fan wrote: > Hi, > > I have a question about the life cycle of pci_dev and its parent pci_bus. > In pci_destroy_dev(), we remove the pci_dev from the bus_list, so > pci_dev is isolated from its parent pci_bus, and their life cycle are > independent too. But it seems that in pci_dev, we can still access the > pci_bus from the pointer pci_dev->bus. To resolve such issue, I think > during the pci_dev removal, there should be process to 1.prevent the > reader incoming 2. ensure the current reader has exit. But can not > find them. > > Could anyone tell me? > > Thanx, pingfan > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >