From: Kalle Valo <kvalo@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
<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: Fri, 31 May 2024 19:47:32 +0300 [thread overview]
Message-ID: <87y17qudwb.fsf@kernel.org> (raw)
In-Reply-To: <6659ee8b8dfd_166872941c@dwillia2-mobl3.amr.corp.intel.com.notmuch> (Dan Williams's message of "Fri, 31 May 2024 08:36:43 -0700")
Dan Williams <dan.j.williams@intel.com> writes:
> Kalle Valo wrote:
> [..]
>> >> The proposed fix for that is here:
>> >>
>> >> http://lore.kernel.org/r/66560aa9dbedb_195e294b0@dwillia2-mobl3.amr.corp.intel.com.notmuch
>> >
>> > I get "Not Found" from that link, is there a typo?
>>
>> I found this fix from for-linus branch:
>>
>> # PCI: Fix missing lockdep annotation for pci_cfg_access_trylock()for-linus
>> https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=for-linus&id=f941b9182c54a885a9d5d4cfd97af66873c98560
>>
>> But at least that doesn't fix my crash.
>
> Sorry for the broken link I mistakenly used a message-id from an
> internal thread with the intel.com reporter. However, it is moot now
> because the new direction is to revert the lockdep infrastructure:
>
> https://lore.kernel.org/r/171711745834.1628941.5259278474013108507.stgit@dwillia2-xfh.jf.intel.com
>
> (that link works...)
Thanks, that links works :) I did a quick test with the three patches
and I didn't see any crashes anymore. But to be confident I need to run
overnight tests, I'll provide my Tested-by after that.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-31 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:42 [regression] BUG: KASAN: use-after-free in lockdep_register_key+0x755/0x8f0 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)
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 [this message]
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=87y17qudwb.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).