linux-kernel - Re: [PATCH 2/7] PCI: move resources and bus_list releasing to pci_release

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:	Tue, 14 May 2013 14:02:32 +0800
From:	Yijing Wang <wangyijing@...wei.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Gu Zheng <guz.fnst@...fujitsu.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/7] PCI: move resources and bus_list releasing to pci_release_dev

On 2013/5/14 11:56, Yinghai Lu wrote:
> On Mon, May 13, 2013 at 8:20 PM, Yijing Wang <wangyijing@...wei.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/