From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Kalle Valo <kvalo@kernel.org>, Dave Jiang <dave.jiang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
regressions@lists.linux.dev,
Jeff Johnson <quic_jjohnson@quicinc.com>,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [regression] BUG: KASAN: use-after-free in lockdep_register_key+0x755/0x8f0
Date: Thu, 30 May 2024 09:18:36 +0200 [thread overview]
Message-ID: <93e4a06b-731d-4fe8-8ceb-e3b56d5ba2bd@leemhuis.info> (raw)
In-Reply-To: <87sexzx02f.fsf@kernel.org>
On 30.05.24 08:53, Kalle Valo wrote:
> Kalle Valo <kvalo@kernel.org> writes:
>> Kalle Valo <kvalo@kernel.org> writes:
> I found my mistake and was able to finish the bisect. This seems to be
> the commit causing my problems:
> # first bad commit: [7e89efc6e9e402839643cb297bab14055c547f07] PCI: Lock upstream bridge for pci_reset_function()
FWIW in case you missed that: there are a few other discussions related
to that commit already:
https://lore.kernel.org/all/?q=7e89efc6e*
And a patch with a Fixes: tag for that commit, too:
https://lore.kernel.org/all/171659995361.845588.6664390911348526329.stgit@dwillia2-xfh.jf.intel.com/
Ciao, Thorsten
next prev parent reply other threads:[~2024-05-30 7:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:42 Kalle Valo
2024-05-29 15:58 ` Kalle Valo
2024-05-30 6:53 ` Kalle Valo
2024-05-30 7:18 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-05-30 7:34 ` Dan Williams
2024-05-30 7:48 ` Kalle Valo
2024-05-30 8:18 ` Kalle Valo
2024-05-31 15:36 ` Dan Williams
2024-05-31 16:47 ` Kalle Valo
2024-06-01 8:39 ` Kalle Valo
2024-06-03 16:53 ` Bjorn Helgaas
2024-06-03 18:29 ` Kalle Valo
2024-06-03 19:14 ` Dan Williams
2024-06-04 8:09 ` Kalle Valo
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=93e4a06b-731d-4fe8-8ceb-e3b56d5ba2bd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ath11k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--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
all inboxes | Powered by JetHome®