From: Bjorn Helgaas <helgaas@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
iommu@lists.linux.dev
Subject: Re: [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() #forregzbot
Date: Wed, 1 Feb 2023 17:24:21 -0600 [thread overview]
Message-ID: <20230201232421.GA1908454@bhelgaas> (raw)
In-Reply-To: <4eac7a29-fed2-6493-a604-17fcba2a13ba@leemhuis.info>
On Mon, Dec 26, 2022 at 02:29:39PM +0100, 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.]
> #regzbot ^introduced v6.0..v6.1-rc1
> #regzbot title pci(?)/iommu(?): hang with kernel 6.1
> #regzbot ignore-activity
#regzbot dup-of: https://bugzilla.kernel.org/show_bug.cgi?id=216859
#regzbot introduced: 145eed48de27
next prev parent reply other threads:[~2023-02-01 23:24 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
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 ` Bjorn Helgaas [this message]
2023-02-13 20:43 ` [PATCH 1/2] iommu/vt-d: Fix PCI device reference count leak in has_external pci() #forregzbot 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=20230201232421.GA1908454@bhelgaas \
--to=helgaas@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.