From: Sudeep Holla <sudeep.holla@kernel.org>
To: SoC Team <soc@lists.linux.dev>,
ALKML <linux-arm-kernel@lists.infradead.org>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
Arnd Bergmann <arnd@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>
Subject: [GIT PULL] ARM: vexpress: Fixes for v7.4
Date: Wed, 7 Oct 2026 16:00:31 +0100 [thread overview]
Message-ID: <20261007150034.624664-1-sudeep.holla@kernel.org> (raw)
Hi ARM SoC Team,
Please pull ! These came in recently and are in -next for a week now.
I am sending these early for v7.4 as fixes instead of waiting until -rc1.
Regards,
Sudeep
-->8
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/vexpress-fixes-7.4
for you to fetch changes up to 27b98d331f1dcebe088ab51a7061a387a7440cb2:
ARM: vexpress: fix device_node refcount leak in vexpress_smp_dt_prepare_cpus() (2026-10-01 09:37:40 +0100)
----------------------------------------------------------------
ARM: vexpress: Fixes for v7.4
Couple of device tree node references acquired during VExpress SMP
preparation were never released. Add `__free(device_node)` to the node
pointers in `vexpress_flags_set()` and `vexpress_smp_dt_prepare_cpus()`
so their references are dropped when each function returns.
Both leaks occur once during boot and have no known functional impact.
----------------------------------------------------------------
Weigang He (2):
ARM: vexpress: fix device_node refcount leak in vexpress_flags_set()
ARM: vexpress: fix device_node refcount leak in vexpress_smp_dt_prepare_cpus()
arch/arm/mach-versatile/platsmp-vexpress.c | 4 ++--
arch/arm/mach-versatile/v2m.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
reply other threads:[~2026-10-07 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261007150034.624664-1-sudeep.holla@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=arnd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=soc@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