From: Sudeep Holla <sudeep.holla@arm.com>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
x86@kernel.org, Andreas Herrmann <aherrmann@suse.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Chen Yu <yu.c.chen@intel.com>, Len Brown <len.brown@intel.com>,
Radu Rendec <rrendec@redhat.com>,
Pierre Gondois <Pierre.Gondois@arm.com>, Pu Wen <puwen@hygon.cn>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Will Deacon <will@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Huang Ying <ying.huang@intel.com>,
Ricardo Neri <ricardo.neri@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/4] cacheinfo: Allocate memory for memory if not done from the primary CPU
Date: Wed, 28 Aug 2024 14:57:19 +0100 [thread overview]
Message-ID: <Zs8svzZPTUmF7NP0@bogus> (raw)
In-Reply-To: <c613d2d5-cb7b-40fe-b322-45ddb43c6382@suse.com>
On Wed, Aug 28, 2024 at 04:16:00PM +0300, Nikolay Borisov wrote:
>
> On 27.08.24 г. 8:16 ч., Ricardo Neri wrote:
> > Commit 5944ce092b97 ("arch_topology: Build cacheinfo from primary CPU")
> > adds functionality that architectures can use to optionally allocate and
> > build cacheinfo early during boot. Commit 6539cffa9495 ("cacheinfo: Add
> > arch specific early level initializer") lets secondary CPUs correct (and
> > reallocate memory) cacheinfo data if needed.
> >
> > If the early build functionality is not used and cacheinfo does not need
> > correction, memory for cacheinfo is never allocated. x86 does not use the
> > early build functionality. Consequently, during the cacheinfo CPU hotplug
> > callback, last_level_cache_is_valid() attempts to dereference a NULL
> > pointer:
> >
> > BUG: kernel NULL pointer dereference, address: 0000000000000100
> > #PF: supervisor read access in kernel mode
> > #PF: error_code(0x0000) - not present page
> > PGD 0 P4D 0
> > Oops: 0000 [#1] PREEPMT SMP NOPTI
> > CPU: 0 PID 19 Comm: cpuhp/0 Not tainted 6.4.0-rc2 #1
> > RIP: 0010: last_level_cache_is_valid+0x95/0xe0a
> >
> > Allocate memory for cacheinfo during the cacheinfo CPU hotplug callback if
> > not done earlier.
>
> I assume instead of duplicating "memory" in the subject you meant
> "cacheinfo" ?
>
Good point, +1 for the $subject change. I clearly missed to notice that.
--
Regards,
Sudeep
next prev parent reply other threads:[~2024-08-28 13:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 5:16 [PATCH v5 0/4] x86/cacheinfo: Set the number of leaves per CPU Ricardo Neri
2024-08-27 5:16 ` [PATCH v5 1/4] cacheinfo: Check for null last-level cache info Ricardo Neri
2024-09-01 18:07 ` Andreas Herrmann
2024-08-27 5:16 ` [PATCH v5 2/4] cacheinfo: Allocate memory for memory if not done from the primary CPU Ricardo Neri
2024-08-28 13:16 ` Nikolay Borisov
2024-08-28 13:57 ` Sudeep Holla [this message]
2024-08-29 4:37 ` Ricardo Neri
2024-09-01 18:08 ` Andreas Herrmann
2024-08-27 5:16 ` [PATCH v5 3/4] x86/cacheinfo: Delete global num_cache_leaves Ricardo Neri
2024-08-28 12:57 ` Nikolay Borisov
2024-08-29 4:33 ` Ricardo Neri
2024-09-01 18:08 ` Andreas Herrmann
2024-08-27 5:16 ` [PATCH v5 4/4] x86/cacheinfo: Clean out init_cache_level() Ricardo Neri
2024-08-28 14:01 ` Nikolay Borisov
2024-08-29 4:38 ` Ricardo Neri
2024-09-01 18:09 ` Andreas Herrmann
2024-09-02 7:41 ` Andreas Herrmann
2024-09-04 7:30 ` Ricardo Neri
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=Zs8svzZPTUmF7NP0@bogus \
--to=sudeep.holla@arm.com \
--cc=Pierre.Gondois@arm.com \
--cc=aherrmann@suse.com \
--cc=catalin.marinas@arm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=puwen@hygon.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=rrendec@redhat.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yu.c.chen@intel.com \
/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.