Received-SPF: pass (google.com: domain of linux-wireless+bounces-8304-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
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
References: <87v82y6wvi.fsf@kernel.org> <87wmncwqxf.fsf@kernel.org>
	<87sexzx02f.fsf@kernel.org>
	<66582bee45da8_6ec329496@dwillia2-mobl3.amr.corp.intel.com.notmuch>
Date: Thu, 30 May 2024 10:48:32 +0300
In-Reply-To: <66582bee45da8_6ec329496@dwillia2-mobl3.amr.corp.intel.com.notmuch>
	(Dan Williams's message of "Thu, 30 May 2024 00:34:06 -0700")
Message-ID: <87jzjbwxin.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

Dan Williams <dan.j.williams@intel.com> writes:

> Kalle Valo wrote:
>
>> Kalle Valo <kvalo@kernel.org> writes:
>> 
>> > Kalle Valo <kvalo@kernel.org> writes:
>> >
>> >> Yesterday I run our ath11k regression tests with v6.10-rc1 and our
>> >> simple ath11k module reload stress started failing reliably with various
>> >> KASAN errors. The test removes and inserts ath11k and other wireless
>> >> modules in a loop. Usually I run it at least 100 times, some times even
>> >> more, and no issues until yesterday.
>> >>
>> >> I have verified that the last wireless-next pull request (tag
>> >> wireless-next-2024-05-08) works without issues and v6.10-rc1 fails
>> >> always, usually within 50 module reload loops. From this I'm _guessing_
>> >> that we have a regression outside wireless, most probably introduced
>> >> between v6.9 and v6.10-rc1. But of course I cannot be sure of anything
>> >> yet.
>> >>
>> >> I see different KASAN warnings and lockdep seems to be always visible in
>> >> the stack traces. I think I can reproduce the issue within 15 minutes or
>> >> so. Before I start bisecting has anyone else seen anything similar? Or
>> >> any suggestions how to debug this further?
>> >>
>> >> I have included some crash logs below, they are retrieved using
>> >> netconsole. Here's a summary of the errors:
>> >>
>> >> [ 159.970765] KASAN: maybe wild-memory-access in range
>> >> [0xbbbbbbbbbbbbbbb8-0xbbbbbbbbbbbbbbbf]
>> >> [  700.017632] BUG: KASAN: use-after-free in lockdep_register_key+0x755/0x8f0
>> >> [  224.695821] BUG: KASAN: slab-out-of-bounds in lockdep_register_key+0x755/0x8f0
>> >> [ 259.666542] BUG: KASAN: slab-use-after-free in
>> >> lockdep_register_key+0x755/0x8f0
>
> 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?

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

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