public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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/484] 5.15.165-rc1 review
Date: Fri, 16 Aug 2024 11:48:17 +0200	[thread overview]
Message-ID: <2024081650-smashup-botch-95ea@gregkh> (raw)
In-Reply-To: <CADYN=9LRUpKMbBebjkcy3qo3O_1UFevA=x90SGZQ7ja5FXHG3w@mail.gmail.com>

On Fri, Aug 16, 2024 at 10:52:35AM +0200, Anders Roxell wrote:
> On Thu, 15 Aug 2024 at 15:40, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.165 release.
> > There are 484 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, 17 Aug 2024 13:18:17 +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-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-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>
> 
> Bisect point to 85cf9455e504 ("KVM: s390: pv: avoid stalls when making
> pages secure")
> as the problematic commit [ Upstream commit
> f0a1a0615a6ff6d38af2c65a522698fb4bb85df6 ].
> 
> Build log:
> ------
> arch/s390/kernel/uv.c: In function 'expected_folio_refs':
> arch/s390/kernel/uv.c:184:15: error: implicit declaration of function
> 'folio_mapcount'; did you mean 'total_mapcount'?
> [-Werror=implicit-function-declaration]
>   184 |         res = folio_mapcount(folio);
>       |               ^~~~~~~~~~~~~~
>       |               total_mapcount
> arch/s390/kernel/uv.c:185:13: error: implicit declaration of function
> 'folio_test_swapcache' [-Werror=implicit-function-declaration]
>   185 |         if (folio_test_swapcache(folio)) {
>       |             ^~~~~~~~~~~~~~~~~~~~
> arch/s390/kernel/uv.c:187:20: error: implicit declaration of function
> 'folio_mapping'; did you mean 'no_idmapping'?
> [-Werror=implicit-function-declaration]
>   187 |         } else if (folio_mapping(folio)) {
>       |                    ^~~~~~~~~~~~~
>       |                    no_idmapping
> arch/s390/kernel/uv.c:189:26: error: invalid use of undefined type
> 'struct folio'
>   189 |                 if (folio->private)
>       |                          ^~
> 

Oops, no folio support in 5.10.y or 5.15.y, I'll go drop these patches
and push out -rc2 releases, thanks for the report!

greg k-h

      reply	other threads:[~2024-08-16  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 13:17 [PATCH 5.15 000/484] 5.15.165-rc1 review Greg Kroah-Hartman
2024-08-15 20:55 ` Florian Fainelli
2024-08-16  8:52 ` Anders Roxell
2024-08-16  9: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=2024081650-smashup-botch-95ea@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