From: Baolu Lu <baolu.lu@linux.intel.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
dwmw2@infradead.org, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, jroedel@suse.de
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
yangyingliang@huawei.com
Subject: Re: [PATCH 0/2] iommu/vt-d: Fix PCI device reference count leak
Date: Thu, 1 Dec 2022 12:04:56 +0800 [thread overview]
Message-ID: <67775808-de49-7de6-66dd-e095ee9bbcc1@linux.intel.com> (raw)
In-Reply-To: <20221121113649.190393-1-wangxiongfeng2@huawei.com>
On 2022/11/21 19:36, Xiongfeng Wang wrote:
> for_each_pci_dev() is implemented by pci_get_device(). The comment of
> pci_get_device() says that it will increase the reference count for the
> returned pci_dev and also decrease the reference count for the input
> pci_dev @from if it is not NULL.
>
> If we break for_each_pci_dev() loop with pdev not NULL, we need to call
> pci_dev_put() to decrease the reference count.
>
> Xiongfeng Wang (2):
> iommu/vt-d: Fix PCI device reference count leak in has_external pci()
> iommu/vt-d: Fix PCI device reference count leak in
> dmar_dev_scope_init()
Queued for Joerg. Thank you!
Best regards,
baolu
prev parent reply other threads:[~2022-12-01 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 11:36 [PATCH 0/2] iommu/vt-d: Fix PCI device reference count leak Xiongfeng Wang
2022-11-21 11:36 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() Xiongfeng Wang
2022-11-21 11:36 ` [PATCH 2/2] iommu/vt-d: Fix PCI device reference count leak in dmar_dev_scope_init() Xiongfeng Wang
2022-12-01 4:04 ` Baolu Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67775808-de49-7de6-66dd-e095ee9bbcc1@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=robin.murphy@arm.com \
--cc=wangxiongfeng2@huawei.com \
--cc=will@kernel.org \
--cc=yangyingliang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox