[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6659ee8b8dfd_166872941c@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Fri, 31 May 2024 08:36:43 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Kalle Valo <kvalo@...nel.org>, Dan Williams <dan.j.williams@...el.com>
CC: Dave Jiang <dave.jiang@...el.com>, Bjorn Helgaas <bhelgaas@...gle.com>,
<linux-wireless@...r.kernel.org>, <ath11k@...ts.infradead.org>,
<regressions@...ts.linux.dev>, Jeff Johnson <quic_jjohnson@...cinc.com>,
<linux-kernel@...r.kernel.org>, <linux-cxl@...r.kernel.org>,
<linux-pci@...r.kernel.org>
Subject: Re: [regression] BUG: KASAN: use-after-free in
lockdep_register_key+0x755/0x8f0
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...)
Powered by blists - more mailing lists