From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Anders Roxell <anders.roxell@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,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 5.15 000/483] 5.15.165-rc2 review
Date: Sat, 17 Aug 2024 09:48:55 +0200 [thread overview]
Message-ID: <2024081743-frisbee-unbutton-476d@gregkh> (raw)
In-Reply-To: <CADYN=9KMRjaxqtcc-Yo9ZDK3b2HH7gzJiwTrUXz7t0x0TO6=uA@mail.gmail.com>
On Sat, Aug 17, 2024 at 07:55:42AM +0200, Anders Roxell wrote:
> On Fri, 16 Aug 2024 at 12:22, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.165 release.
> > There are 483 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 Sun, 18 Aug 2024 10:14:00 +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/v5.x/stable-review/patch-5.15.165-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-5.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The following S390 build failed on stable-rc 5.15.y with gcc-12 and clang due
> to following warnings and errors [1].
>
> s390:
> build:
> * gcc-8-defconfig-fe40093d
> * gcc-12-defconfig
> * clang-18-defconfig
>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> The bisect points to 85cf9455e504 ("KVM: s390: pv: avoid stalls when
> making pages secure")
> as the problematic commit [ Upstream commit
> f0a1a0615a6ff6d38af2c65a522698fb4bb85df6 ].
>
> Build log:
> --------
> /builds/linux/arch/s390/kernel/uv.c: In function 'make_page_secure':
> /builds/linux/arch/s390/kernel/uv.c:219:19: error: 'UVC_CC_OK'
> undeclared (first use in this function)
> 219 | if (cc == UVC_CC_OK)
> | ^~~~~~~~~
> /builds/linux/arch/s390/kernel/uv.c:219:19: note: each undeclared
> identifier is reported only once for each function it appears in
> /builds/linux/arch/s390/kernel/uv.c:221:24: error: 'UVC_CC_BUSY'
> undeclared (first use in this function); did you mean 'SIGP_CC_BUSY'?
> 221 | else if (cc == UVC_CC_BUSY || cc == UVC_CC_PARTIAL)
> | ^~~~~~~~~~~
> | SIGP_CC_BUSY
> /builds/linux/arch/s390/kernel/uv.c:221:45: error: 'UVC_CC_PARTIAL'
> undeclared (first use in this function)
> 221 | else if (cc == UVC_CC_BUSY || cc == UVC_CC_PARTIAL)
> | ^~~~~~~~~~~~~~
> /builds/linux/arch/s390/kernel/uv.c: In function 'should_export_before_import':
> /builds/linux/arch/s390/kernel/uv.c:249:40: error: 'mm_context_t' has
> no member named 'protected_count'
> 249 | return atomic_read(&mm->context.protected_count) > 1;
> | ^
> /builds/linux/arch/s390/kernel/uv.c:250:1: error: control reaches end
> of non-void function [-Werror=return-type]
> 250 | }
> | ^
> cc1: some warnings being treated as errors
>
>
> Build log link:
> --------
> [1] https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.164-484-gaff234a5be72/testrun/24890486/suite/build/test/gcc-12-defconfig/log
I'll go fix this up and push out a rc3, thanks.
greg k-h
prev parent reply other threads:[~2024-08-17 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:22 [PATCH 5.15 000/483] 5.15.165-rc2 review Greg Kroah-Hartman
2024-08-16 14:17 ` Mark Brown
2024-08-16 19:43 ` Jon Hunter
2024-08-16 20:53 ` Ron Economos
2024-08-16 23:21 ` Florian Fainelli
2024-08-17 5:55 ` Anders Roxell
2024-08-17 7:48 ` Greg Kroah-Hartman [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=2024081743-frisbee-unbutton-476d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=imbrenda@linux.ibm.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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