linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 30 May 2024 10:48:32 +0300	[thread overview]
Message-ID: <87jzjbwxin.fsf@kernel.org> (raw)
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")

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

  reply	other threads:[~2024-05-30  7:48 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 [this message]
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=87jzjbwxin.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).