From: Zeno Davatz <zdavatz@gmail.com>
To: wangxiongfeng2@huawei.com
Cc: baolu.lu@linux.intel.com, dwmw2@infradead.org,
iommu@lists.linux.dev, joro@8bytes.org, jroedel@suse.de,
robin.murphy@arm.com, will@kernel.org, yangyingliang@huawei.com
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci()
Date: Sun, 25 Dec 2022 13:11:03 +0100 [thread overview]
Message-ID: <D41A3A42-2412-4722-9090-01565058E525@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
Hi
I am getting this hang with kernel 6.1. See attachment.
Is this related to your patch?
Kernel 6.1 does not boot for me. Kernel 6.0 was fine.
Thank you for your reply.
Best
Zeno
[-- Attachment #2: image0.jpeg --]
[-- Type: image/jpeg, Size: 1538042 bytes --]
next reply other threads:[~2022-12-25 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 12:11 Zeno Davatz [this message]
2022-12-25 13:16 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() Baolu Lu
2022-12-25 13:37 ` Zeno Davatz
2022-12-25 13:52 ` Baolu Lu
2022-12-25 14:03 ` Zeno Davatz
2022-12-25 14:26 ` Zeno Davatz
2022-12-25 18:56 ` Zeno Davatz
2022-12-25 13:40 ` Zeno Davatz
2022-12-26 13:29 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() #forregzbot Thorsten Leemhuis
2022-12-27 7:20 ` Baolu Lu
2022-12-27 7:37 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() Thorsten Leemhuis
2023-02-01 23:24 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() #forregzbot Bjorn Helgaas
2023-02-13 20:43 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
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
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=D41A3A42-2412-4722-9090-01565058E525@gmail.com \
--to=zdavatz@gmail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).