From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.15 000/123] 5.15.82-rc2 review
Date: Tue, 6 Dec 2022 17:33:20 +0100 [thread overview]
Message-ID: <Y49u0LhWMDJxc90l@kroah.com> (raw)
In-Reply-To: <792a6fba-aa15-2e2a-7527-99ab1116a01d@roeck-us.net>
On Tue, Dec 06, 2022 at 07:11:39AM -0800, Guenter Roeck wrote:
> On 12/6/22 04:42, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.82 release.
> > There are 123 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Thu, 08 Dec 2022 12:40:31 +0000.
> > Anything received after that time might be too late.
> >
>
> arch/riscv/kernel/smp.c: In function 'handle_IPI':
> arch/riscv/kernel/smp.c:195:44: error: 'cpu' undeclared (first use in this function)
> 195 | ipi_cpu_crash_stop(cpu, get_irq_regs());
> | ^~~
> arch/riscv/kernel/smp.c:195:44: note: each undeclared identifier is reported only once for each function it appears in
> arch/riscv/kernel/smp.c:217:22: error: 'old_regs' undeclared (first use in this function)
> 217 | set_irq_regs(old_regs);
> | ^~~~~~~~
>
> This is with v5.15.81-124-g9269e46bc838.
>
> The backport of commit 9b932aadfc47d seems wrong. The original version introduces
> the cpu variable in handle_IPI(). The backport doesn't, and removes old_regs
> instead.
>
> Backport:
>
> void handle_IPI(struct pt_regs *regs)
> {
> - struct pt_regs *old_regs = set_irq_regs(regs);
> unsigned long *pending_ipis = &ipi_data[smp_processor_id()].bits;
> unsigned long *stats = ipi_data[smp_processor_id()].stats;
>
> Original:
>
> void handle_IPI(struct pt_regs *regs)
> {
> - unsigned long *pending_ipis = &ipi_data[smp_processor_id()].bits;
> - unsigned long *stats = ipi_data[smp_processor_id()].stats;
> + unsigned int cpu = smp_processor_id();
> + unsigned long *pending_ipis = &ipi_data[cpu].bits;
> + unsigned long *stats = ipi_data[cpu].stats;
>
> Upstream includes commit 7ecbc648102f which removes the old_regs variable.
> That doesn't mean it can be removed in the backport.
Yeah, that looks odd. I've dropped it from both 5.15 and 6.0 now and
will push out a new -rc with that removed.
thanks for testing!
greg k-h
next prev parent reply other threads:[~2022-12-06 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 12:42 [PATCH 5.15 000/123] 5.15.82-rc2 review Greg Kroah-Hartman
2022-12-06 15:11 ` Guenter Roeck
2022-12-06 16:33 ` Greg Kroah-Hartman [this message]
2022-12-06 16:46 ` Jon Hunter
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=Y49u0LhWMDJxc90l@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@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@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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