From: Baolu Lu <baolu.lu@linux.intel.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() #forregzbot
Date: Tue, 27 Dec 2022 15:20:27 +0800 [thread overview]
Message-ID: <77905fdc-ca91-75ef-4d79-378c108ee4b2@linux.intel.com> (raw)
In-Reply-To: <4eac7a29-fed2-6493-a604-17fcba2a13ba@leemhuis.info>
On 2022/12/26 21:29, Thorsten Leemhuis wrote:
> [Note: this mail contains only information for Linux kernel regression
> tracking. Mails like these contain '#forregzbot' in the subject to make
> then easy to spot and filter out. The author also tried to remove most
> or all individuals from the list of recipients to spare them the hassle.]
>
> On 25.12.22 13: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.
>>
>> Thank you for your reply.
>
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced v6.0..v6.1-rc1
> #regzbot title pci(?)/iommu(?): hang with kernel 6.1
> #regzbot ignore-activity
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
>
The reporter said that "The problem happens somewhere between Kernel
Version 6.0 and 6.1-rc1." This patch only shows up since v6.1-rc8. This
patch cannot generate any kernel regression on v6.1-rc1.
--
Best regards,
baolu
next prev parent reply other threads:[~2022-12-27 7:20 UTC|newest]
Thread overview: 13+ 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
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 [this message]
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
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=77905fdc-ca91-75ef-4d79-378c108ee4b2@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).