From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: 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>,
linux-mips@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 6.6 000/175] 6.6.144-rc1 review
Date: Sat, 11 Jul 2026 00:53:30 +0200 [thread overview]
Message-ID: <84daa623-6767-437e-915b-933dbebd2e8a@gmail.com> (raw)
In-Reply-To: <20260710163023.agent5-0013@kernel.org>
Hi Sasha,
On 10.07.26 23:03, Sasha Levin wrote:
> 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.
>
Sure, I adopted it accordingly and sent patches for 6.6.y and 6.1.y.
Best regards,
Jonas
prev parent reply other threads:[~2026-07-10 22:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 16:18 [PATCH 6.6 000/175] 6.6.144-rc1 review Greg Kroah-Hartman
2026-07-02 19:46 ` Brett A C Sheffield
2026-07-02 20:46 ` Peter Schneider
2026-07-02 23:49 ` Miguel Ojeda
2026-07-03 6:33 ` Ron Economos
2026-07-03 7:13 ` Shung-Hsi Yu
2026-07-03 7:40 ` Francesco Dolcini
2026-07-03 8:01 ` Wentao Guan
2026-07-03 9:39 ` Greg KH
2026-07-03 9:42 ` Pavel Machek
2026-07-03 13:43 ` Mark Brown
2026-07-09 9:45 ` Florian Fainelli
2026-07-10 21:03 ` Sasha Levin
2026-07-10 22:53 ` Jonas Jelonek [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=84daa623-6767-437e-915b-933dbebd2e8a@gmail.com \
--to=jelonek.jonas@gmail.com \
--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=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=sashal@kernel.org \
--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