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, allen.lkml@gmail.com, broonie@kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Kees Cook <keescook@chromium.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH 6.6 000/163] 6.6.37-rc1 review
Date: Thu, 4 Jul 2024 09:30:19 +0200 [thread overview]
Message-ID: <2024070458-compile-amused-7d1c@gregkh> (raw)
In-Reply-To: <CA+G9fYvcbdKN8B9t-ukO2aZCOwkjNme8+XhLcL-=wcd+XXRP6g@mail.gmail.com>
On Wed, Jul 03, 2024 at 06:04:57PM +0530, Naresh Kamboju wrote:
> On Wed, 3 Jul 2024 at 14:27, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > On Tue, 2 Jul 2024 at 22:48, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.6.37 release.
> > > There are 163 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, 04 Jul 2024 17:01:55 +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.37-rc1.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
> >
> > The following powerpc builds failed on stable-rc 6.6.
> >
> > powerpc:
> > - gcc-13-defconfig
> > - clang-18-defconfig
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > Build log:
> > ---------
> > arch/powerpc/net/bpf_jit_comp.c: In function 'bpf_int_jit_compile':
> > arch/powerpc/net/bpf_jit_comp.c:208:17: error: ignoring return value
> > of 'bpf_jit_binary_lock_ro' declared with attribute
> > 'warn_unused_result' [-Werror=unused-result]
> > 208 | bpf_jit_binary_lock_ro(bpf_hdr);
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: all warnings being treated as errors
> >
>
> Anders bisected this down to,
> first bad commit: [28ae2e78321b5ac25958b3fcae0dcc80116e0c50]
> bpf: Take return from set_memory_rox() into account with
> bpf_jit_binary_lock_ro()
Thanks, that's due to some changes that happened in 6.7 in this area,
I've queued those changes up now and will push out a -rc2 later today.
greg k-h
next prev parent reply other threads:[~2024-07-04 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 17:01 [PATCH 6.6 000/163] 6.6.37-rc1 review Greg Kroah-Hartman
2024-07-02 19:18 ` SeongJae Park
2024-07-02 21:39 ` Mark Brown
2024-07-02 23:43 ` Shuah Khan
2024-07-03 8:13 ` Jon Hunter
2024-07-03 8:57 ` Naresh Kamboju
2024-07-03 12:34 ` Naresh Kamboju
2024-07-04 7:30 ` Greg Kroah-Hartman [this message]
2024-07-03 12:54 ` Takeshi Ogasawara
2024-07-03 15:05 ` Peter Schneider
2024-07-03 17:29 ` Harshit Mogalapalli
2024-07-03 17:31 ` Kelsey Steele
2024-07-03 21:16 ` Ron Economos
2024-07-04 15:12 ` Florian Fainelli
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=2024070458-compile-amused-7d1c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=ast@kernel.org \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@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