Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755721Ab3ENGDh (ORCPT ); Tue, 14 May 2013 02:03:37 -0400 Received: from szxga02-in.huawei.com ([119.145.14.65]:30044 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752548Ab3ENGDg (ORCPT ); Tue, 14 May 2013 02:03:36 -0400 Message-ID: <5191D378.8060600@huawei.com> Date: Tue, 14 May 2013 14:02:32 +0800 From: Yijing Wang User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Yinghai Lu CC: Bjorn Helgaas , Gu Zheng , "linux-pci@vger.kernel.org" , Linux Kernel Mailing List Subject: Re: [PATCH 2/7] PCI: move resources and bus_list releasing to pci_release_dev References: <1368498506-25857-1-git-send-email-yinghai@kernel.org> <1368498506-25857-3-git-send-email-yinghai@kernel.org> <5191AD65.7090105@huawei.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.135.76.69] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 953 Lines: 38 On 2013/5/14 11:56, Yinghai Lu wrote: > On Mon, May 13, 2013 at 8:20 PM, Yijing Wang wrote: >> On 2013/5/14 10:28, Yinghai Lu wrote: >>> We should not release resource in pci_destroy that is too early >> >> Hi Yinghai, >> "too early" means that after pci_stop_dev(), if someone else >> hold the device reference, it still care the device resource ? e.g.? > > I don't mean that. > >> >>> as there could be still other use hold reference. > > purpose is: > move res releasing as late as possible. so pci_stop_and_remove_bus_device > could be called several times for nested removing via sys. OK, thanks for explanation. Thanks! Yijing. > > Yinghai > > -- Thanks! Yijing -- 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/