lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a5k5ukew.fsf@kernel.org>
Date: Sat, 01 Jun 2024 11:39:03 +0300
From: Kalle Valo <kvalo@...nel.org>
To: 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 <kvalo@...nel.org> writes:

> Dan Williams <dan.j.williams@...el.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.

Ok, I'm now quite confident that the issues I saw are solved so:

Tested-by: Kalle Valo <kvalo@...nel.org>

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ