iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zeno Davatz <zdavatz@gmail.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: wangxiongfeng2@huawei.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 19:56:17 +0100	[thread overview]
Message-ID: <CAOkhzLUTNpq_hA9v1jZn9+919Hk43=+ouHG2f_u_g1Xt-m5tDA@mail.gmail.com> (raw)
In-Reply-To: <1c3be2ab-43af-cac7-fa0b-f3118b4e714e@linux.intel.com>

Dear Baolu

On Sun, Dec 25, 2022 at 2:52 PM Baolu Lu <baolu.lu@linux.intel.com> wrote:
>
> On 2022/12/25 21:37, Zeno Davatz wrote:
> > On Sun, Dec 25, 2022 at 2:16 PM Baolu Lu<baolu.lu@linux.intel.com>  wrote:
> >> On 2022/12/25 20:11, Zeno Davatz wrote:
> >>> 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.
> >> It seems unlikely.
> >>
> >> Have you located the patch through the bisect tool? Or does it boot well
> >> if you revert this patch?
> > I did not bisect the patch. All I currently know is that version 5.5
> > and version 6.0 of the Kernel booted fine for me.
> >
> > I test every Kernel release and normally the boot process goes flawless.
> >
> > The patch I am referring to is also mentioned by Linus in the Kernel
> > log, AFAICT tell the only PCI patch.
> >
> > https://lkml.org/lkml/2022/12/11/206
>
> I didn't find any reference to this patch in above thread. Can you
> please elaborate a bit more?
>
> By the way, from the video you shared, the hang happens in the PCI
> enumeration process. This patch touched the code that only executes
> after that.
>
> Can you please simply revert this patch and check the boot again?

The problem happens somewhere between Kernel Version 6.0 and 6.1-rc1.

So my Boot is fine with Kernel 6.0 but stops working with Kernel
version 6.1-rc1.

Best
Zeno

  parent reply	other threads:[~2022-12-25 18:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 12:11 [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() Zeno Davatz
2022-12-25 13:16 ` 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 [this message]
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='CAOkhzLUTNpq_hA9v1jZn9+919Hk43=+ouHG2f_u_g1Xt-m5tDA@mail.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).