From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@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, hca@linux.ibm.com,
gbatra@linux.vnet.ibm.com
Subject: Re: [PATCH 6.1 000/368] 6.1.64-rc3 review
Date: Sun, 26 Nov 2023 15:41:26 +0000 [thread overview]
Message-ID: <2023112624-plutonium-garland-694d@gregkh> (raw)
In-Reply-To: <a853e6f3-f658-4049-9c36-66835d144eac@linaro.org>
On Sat, Nov 25, 2023 at 11:41:11PM -0600, Daniel Díaz wrote:
> Hello!
>
> On 25/11/23 1:45 p. m., Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.64 release.
> > There are 368 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 Mon, 27 Nov 2023 19:43:06 +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.1.64-rc3.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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> The following configurations are failing for System/390:
> * gcc-8-allmodconfig
> * gcc-8-allnoconfig
> * gcc-8-defconfig (+CONFIG_DEBUG_INFO_BTF=n)
> * gcc-8-tinyconfig
> * gcc-13-allmodconfig
> * gcc-13-allnoconfig
> * gcc-13-defconfig
> * gcc-13-tinyconfig
> * clang-17-allmodconfig
> * clang-17-allnoconfig
> * clang-17-defconfig
> * clang-17-tinyconfig
> * clang-nightly-allmodconfig
> * clang-nightly-allnoconfig
> * clang-nightly-defconfig
> * clang-nightly-tinyconfig
>
> The error looks like this:
> -----8<-----
> In file included from /builds/linux/arch/s390/include/asm/page.h:208,
> from /builds/linux/arch/s390/include/asm/thread_info.h:26,
> from /builds/linux/include/linux/thread_info.h:60,
> from /builds/linux/arch/s390/include/asm/preempt.h:6,
> from /builds/linux/include/linux/preempt.h:78,
> from /builds/linux/include/linux/spinlock.h:56,
> from /builds/linux/include/linux/mmzone.h:8,
> from /builds/linux/include/linux/gfp.h:7,
> from /builds/linux/include/linux/mm.h:7,
> from /builds/linux/arch/s390/mm/page-states.c:13:
> /builds/linux/arch/s390/mm/page-states.c: In function 'cmma_init_nodat':
> /builds/linux/arch/s390/mm/page-states.c:198:30: error: 'invalid_pg_dir' undeclared (first use in this function)
> 198 | page = virt_to_page(&invalid_pg_dir);
> | ^~~~~~~~~~~~~~
> /builds/linux/include/asm-generic/memory_model.h:25:45: note: in definition of macro '__pfn_to_page'
> 25 | #define __pfn_to_page(pfn) (vmemmap + (pfn))
> | ^~~
> /builds/linux/arch/s390/include/asm/page.h:198:34: note: in expansion of macro 'phys_to_pfn'
> 198 | #define virt_to_pfn(kaddr) (phys_to_pfn(__pa(kaddr)))
> | ^~~~~~~~~~~
> /builds/linux/arch/s390/include/asm/page.h:198:46: note: in expansion of macro '__pa'
> 198 | #define virt_to_pfn(kaddr) (phys_to_pfn(__pa(kaddr)))
> | ^~~~
> /builds/linux/arch/s390/include/asm/page.h:201:45: note: in expansion of macro 'virt_to_pfn'
> 201 | #define virt_to_page(kaddr) pfn_to_page(virt_to_pfn(kaddr))
> | ^~~~~~~~~~~
> /builds/linux/arch/s390/mm/page-states.c:198:16: note: in expansion of macro 'virt_to_page'
> 198 | page = virt_to_page(&invalid_pg_dir);
> | ^~~~~~~~~~~~
> /builds/linux/arch/s390/mm/page-states.c:198:30: note: each undeclared identifier is reported only once for each function it appears in
> 198 | page = virt_to_page(&invalid_pg_dir);
> | ^~~~~~~~~~~~~~
> /builds/linux/include/asm-generic/memory_model.h:25:45: note: in definition of macro '__pfn_to_page'
> 25 | #define __pfn_to_page(pfn) (vmemmap + (pfn))
> | ^~~
> /builds/linux/arch/s390/include/asm/page.h:198:34: note: in expansion of macro 'phys_to_pfn'
> 198 | #define virt_to_pfn(kaddr) (phys_to_pfn(__pa(kaddr)))
> | ^~~~~~~~~~~
> /builds/linux/arch/s390/include/asm/page.h:198:46: note: in expansion of macro '__pa'
> 198 | #define virt_to_pfn(kaddr) (phys_to_pfn(__pa(kaddr)))
> | ^~~~
> /builds/linux/arch/s390/include/asm/page.h:201:45: note: in expansion of macro 'virt_to_pfn'
> 201 | #define virt_to_page(kaddr) pfn_to_page(virt_to_pfn(kaddr))
> | ^~~~~~~~~~~
> /builds/linux/arch/s390/mm/page-states.c:198:16: note: in expansion of macro 'virt_to_page'
> 198 | page = virt_to_page(&invalid_pg_dir);
> | ^~~~~~~~~~~~
> make[4]: *** [/builds/linux/scripts/Makefile.build:250: arch/s390/mm/page-states.o] Error 1
> ----->8-----
>
> Bisection points to:
>
> commit 1a5dd59623dc206de30df2d13316a3ce9be6821a
> Author: Heiko Carstens <hca@linux.ibm.com>
> Date: Tue Oct 24 10:15:20 2023 +0200
>
> s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir
> commit 84bb41d5df48868055d159d9247b80927f1f70f9 upstream.
Ugh, s390, let me go drop that from everywhere now...
> Reverting that commit made the build pass.
>
> Reproducer:
> tuxmake --runtime podman --target-arch s390 --toolchain gcc-13 --kconfig tinyconfig
>
>
> Then, there's a PowerPC failure too on the following configurations:
> * gcc-8-allmodconfig
> * gcc-8-defconfig
> * gcc-13-allmodconfig
> * gcc-13-defconfig
> * clang-17-defconfig
> * clang-nightly-defconfig
>
> That looks like this:
> -----8<-----
> /builds/linux/arch/powerpc/platforms/pseries/iommu.c: In function 'find_existing_ddw':
> /builds/linux/arch/powerpc/platforms/pseries/iommu.c:926:49: error: 'struct dma_win' has no member named 'direct'
> 926 | *direct_mapping = window->direct;
> | ^~
> make[5]: *** [/builds/linux/scripts/Makefile.build:250: arch/powerpc/platforms/pseries/iommu.o] Error 1
> ----->8-----
>
> I guess it might be due to this:
>
> commit fd018dfa8f0b963d65700d518596f9d834844fca
> Author: Gaurav Batra <gbatra@linux.vnet.ibm.com>
> Date: Mon Oct 2 22:08:02 2023 -0500
>
> powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device
> commit 3bf983e4e93ce8e6d69e9d63f52a66ec0856672e upstream.
>
>
> Reverting that commit does make the build pass again.
Ick, also dropped from everywhere now, thanks.
greg k-h
prev parent reply other threads:[~2023-11-26 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 19:45 [PATCH 6.1 000/368] 6.1.64-rc3 review Greg Kroah-Hartman
2023-11-25 21:28 ` Florian Fainelli
2023-11-25 21:56 ` Pavel Machek
2023-11-26 5:41 ` Daniel Díaz
2023-11-26 15:41 ` 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=2023112624-plutonium-garland-694d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=conor@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gbatra@linux.vnet.ibm.com \
--cc=hca@linux.ibm.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