From: Oscar Salvador <osalvador@suse.de>
To: Marco Elver <elver@google.com>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Andrey Konovalov <andreyknvl@gmail.com>,
Alexander Potapenko <glider@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next:master] [mm,page_owner] 4bedfb314b: BUG:KASAN:null-ptr-deref_in_init_page_owner
Date: Wed, 6 Mar 2024 08:19:37 +0100 [thread overview]
Message-ID: <ZegZCaFJrnAWL4kb@localhost.localdomain> (raw)
In-Reply-To: <Zedmst0pEtGuY6B6@localhost.localdomain>
On Tue, Mar 05, 2024 at 07:38:42PM +0100, Oscar Salvador wrote:
> But they point out to
>
> commit 4bedfb314bdd85c1662ecc46fa25b33b998f994d (HEAD, bisection)
> Author: Oscar Salvador <osalvador@suse.de>
> Date: Thu Feb 15 22:59:03 2024 +0100
>
> mm,page_owner: maintain own list of stack_records structs
>
> which the only thing it does is to retrieve the stack_record for
> {dummy,failure}.handle and increment their refcount and link them.
> I am pretty sure the problem comes from either dummy_handle or
> failure_handle being 0 and the stack_record we get is NULL.
Yes, jfyi: I "artificially" reproduced this by making
dummy_handle explicitly = 0 again.
And I see that KASAN points to the same location.
I am kind of surprised stackdepot ran out of space that early, but I
guess we cannot take anything for granted.
I am alrady working on a fixup to now blow up here.
--
Oscar Salvador
SUSE Labs
prev parent reply other threads:[~2024-03-06 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 6:08 [linux-next:master] [mm,page_owner] 4bedfb314b: BUG:KASAN:null-ptr-deref_in_init_page_owner kernel test robot
2024-03-05 9:27 ` Oscar Salvador
2024-03-05 13:02 ` Marco Elver
2024-03-05 18:32 ` Oscar Salvador
2024-03-05 18:38 ` Oscar Salvador
2024-03-06 7:19 ` Oscar Salvador [this message]
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=ZegZCaFJrnAWL4kb@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@suse.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=vbabka@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.