From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: stable@vger.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@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
"Björn Töpel" <bjorn@rivosinc.com>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 6.6 000/129] 6.6.90-rc2 review
Date: Fri, 9 May 2025 08:19:05 +0200 [thread overview]
Message-ID: <2025050917-dismay-scary-7261@gregkh> (raw)
In-Reply-To: <CA+G9fYsKqxUExVW1rEhU8_5pYOuhkzXyeL9TmTyGVsV2-C-PFQ@mail.gmail.com>
On Thu, May 08, 2025 at 06:16:12PM +0530, Naresh Kamboju wrote:
> On Thu, 8 May 2025 at 17:00, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.6.90 release.
> > There are 129 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 Sat, 10 May 2025 11:25:47 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.90-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Regressions on riscv with allyesconfig and allmodconfig builds failed with
> clang-20 and gcc-13 toolchain on the stable-rc 6.6.90-rc1 and 6.6.90-rc2
>
> * riscv, build
> - clang-20-allmodconfig
> - gcc-13-allmodconfig
> - gcc-13-allyesconfig
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? Yes
>
> Build regression: riscv uprobes.c unused variable 'start'
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build error riscv
> arch/riscv/kernel/probes/uprobes.c: In function 'arch_uprobe_copy_ixol':
> arch/riscv/kernel/probes/uprobes.c:170:23: error: unused variable
> 'start' [-Werror=unused-variable]
> 170 | unsigned long start = (unsigned long)dst;
> | ^~~~~
> cc1: all warnings being treated as errors
Oh that's wierd. riscv defines flush_icache_range() as "empty" so then
this patch does nothing in these older kernels. Ah, it's an inline
function in newer kernel trees as well so that the build warning isn't
there anymore.
As this change feels odd for 6.6 and older kernels, AND it's causing
build warnings, I'm just going to drop it and if the riscv maintainers
really want it applied to these trees, will take a working backport from
them.
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-09 6:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 11:30 [PATCH 6.6 000/129] 6.6.90-rc2 review Greg Kroah-Hartman
2025-05-08 12:46 ` Naresh Kamboju
2025-05-09 6:19 ` Greg Kroah-Hartman [this message]
2025-05-09 6:46 ` Ron Economos
2025-05-08 13:57 ` Peter Schneider
2025-05-08 15:00 ` Ryan Matthews
2025-05-08 17:00 ` Miguel Ojeda
2025-05-08 17:41 ` Jon Hunter
2025-05-10 1:24 ` Mark Brown
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=2025050917-dismay-scary-7261@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn@rivosinc.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=palmer@rivosinc.com \
--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