From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@nabladev.com,
jonathanh@nvidia.com, sudipm.mukherjee@gmail.com, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
achill@achill.org, sr@sladewatkins.com,
Florian Fainelli <f.fainelli@gmail.com>,
Jonas Jelonek <jelonek.jonas@gmail.com>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH 6.6 000/175] 6.6.144-rc1 review
Date: Fri, 10 Jul 2026 17:03:09 -0400 [thread overview]
Message-ID: <20260710163023.agent5-0013@kernel.org> (raw)
In-Reply-To: <34b7e26f-df63-4523-b4d2-5de13c192a8c@gmail.com>
On Thu, Jul 09, 2026 at 11:45:14AM +0200, Florian Fainelli wrote:
> On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, same build failure
> as 6.1 for MIPS:
>
> arch/mips/kernel/smp.c: In function 'stop_this_cpu':
> arch/mips/kernel/smp.c:396:2: error: implicit declaration of function
> 'rcutree_report_cpu_dead'; did you mean 'rcutree_prepare_cpu'?
> [-Werror=implicit-function-declaration]
> rcutree_report_cpu_dead();
> ^~~~~~~~~~~~~~~~~~~~~~~
> rcutree_prepare_cpu
The offending backport was dropped before 6.6.144 was released, so the
build failure itself is gone.
That still leaves 6.6.y and 6.1.y without 9f3f3bdc6d9d ("MIPS: smp:
report dying CPU to RCU in stop_this_cpu()") while both trees already
ship 91840be8f710 ("irq_work: Fix use-after-free in irq_work_single()
on PREEMPT_RT"), which is what exposes the MIPS reboot hang that
9f3f3bdc6d9d fixes.
Jonas, could you send backports of 9f3f3bdc6d9d for 6.6.y and 6.1.y
with that adaptation? I'd rather take the author's version than adapt
it here.
--
Thanks,
Sasha
next parent reply other threads:[~2026-07-10 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260702155115.766838875@linuxfoundation.org>
[not found] ` <34b7e26f-df63-4523-b4d2-5de13c192a8c@gmail.com>
2026-07-10 21:03 ` Sasha Levin [this message]
2026-07-10 22:53 ` [PATCH 6.6 000/175] 6.6.144-rc1 review Jonas Jelonek
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=20260710163023.agent5-0013@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jelonek.jonas@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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