Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window close
The results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective.
,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________
Compile testing ---------------
We compiled the kernel for 4 architectures:
aarch64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
ppc64le: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
s390x: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
x86_64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)
Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Veronika
We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective.
,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-'
Compile testing
We compiled the kernel for 4 architectures:
aarch64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg ppc64le: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg s390x: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg x86_64: make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
If not, please let me know.
thanks,
greg k-h
On Thu, Jul 15, 2021 at 7:32 PM Greg KH greg@kroah.com wrote:
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
Yes. All runs of the queue hit the problem, including the latest b438694730fd. I also ran a test of the second latest completed run with a patch revert and the issue disappeared.
That said, the c139bde0fdca rebase (second latest) introduced an s390x compilation problem that did not happen before. It is also visible with the latest head. I don't know what commit introduced it yet as the run barely finished:
00:00:12 In file included from arch/s390/kernel/signal.c:35: 00:00:12 arch/s390/kernel/signal.c: In function ‘setup_frame’: 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_sigreturn’ undeclared (first use in this function) 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:340:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 340 | restorer = VDSO64_SYMBOL(current, sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: note: each undeclared identifier is reported only once for each function it appears in 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:340:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 340 | restorer = VDSO64_SYMBOL(current, sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c: In function ‘setup_rt_frame’: 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_rt_sigreturn’ undeclared (first use in this function) 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:398:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 398 | restorer = VDSO64_SYMBOL(current, rt_sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c: In function ‘arch_do_signal_or_restart’: 00:00:12 ./arch/s390/include/asm/vdso.h:16:67: error: ‘vdso32_offset_restart_syscall’ undeclared (first use in this function); did you mean ‘do_no_restart_syscall’? 00:00:12 16 | #define VDSO32_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso32_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:514:22: note: in expansion of macro ‘VDSO32_SYMBOL’ 00:00:12 514 | regs->psw.addr = VDSO32_SYMBOL(current, restart_syscall); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_restart_syscall’ undeclared (first use in this function); did you mean ‘do_no_restart_syscall’? 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:516:22: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 516 | regs->psw.addr = VDSO64_SYMBOL(current, restart_syscall); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 make[4]: *** [scripts/Makefile.build:273: arch/s390/kernel/signal.o] Error 1
Veronika
If not, please let me know.
thanks,
greg k-h
On Thu, Jul 15, 2021 at 2:38 PM Veronika Kabatova vkabatov@redhat.com wrote:
On Thu, Jul 15, 2021 at 7:32 PM Greg KH greg@kroah.com wrote:
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
Yes. All runs of the queue hit the problem, including the latest b438694730fd. I also ran a test of the second latest completed run with a patch revert and the issue disappeared.
That said, the c139bde0fdca rebase (second latest) introduced an s390x compilation problem that did not happen before. It is also visible with the latest head. I don't know what commit introduced it yet as the run barely finished:
I hit this same failure building in koji. All of the s390 patches are related, and appear to be an incomplete set:
s390-signal-switch-to-using-vdso-for-sigreturn-and-syscall-restart.patch s390-vdso64-add-sigreturn-rt_sigreturn-and-restart_syscall.patch s390-vdso-add-minimal-compat-vdso.patch s390-vdso-always-enable-vdso.patch s390-vdso-rename-vdso64_lbase-to-vdso_lbase.patch
Justin
00:00:12 In file included from arch/s390/kernel/signal.c:35: 00:00:12 arch/s390/kernel/signal.c: In function ‘setup_frame’: 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_sigreturn’ undeclared (first use in this function) 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:340:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 340 | restorer = VDSO64_SYMBOL(current, sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: note: each undeclared identifier is reported only once for each function it appears in 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:340:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 340 | restorer = VDSO64_SYMBOL(current, sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c: In function ‘setup_rt_frame’: 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_rt_sigreturn’ undeclared (first use in this function) 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:398:14: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 398 | restorer = VDSO64_SYMBOL(current, rt_sigreturn); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c: In function ‘arch_do_signal_or_restart’: 00:00:12 ./arch/s390/include/asm/vdso.h:16:67: error: ‘vdso32_offset_restart_syscall’ undeclared (first use in this function); did you mean ‘do_no_restart_syscall’? 00:00:12 16 | #define VDSO32_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso32_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:514:22: note: in expansion of macro ‘VDSO32_SYMBOL’ 00:00:12 514 | regs->psw.addr = VDSO32_SYMBOL(current, restart_syscall); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 ./arch/s390/include/asm/vdso.h:14:67: error: ‘vdso64_offset_restart_syscall’ undeclared (first use in this function); did you mean ‘do_no_restart_syscall’? 00:00:12 14 | #define VDSO64_SYMBOL(tsk, name) ((tsk)->mm->context.vdso_base + (vdso64_offset_##name)) 00:00:12 | ^~~~~~~~~~~~~~ 00:00:12 arch/s390/kernel/signal.c:516:22: note: in expansion of macro ‘VDSO64_SYMBOL’ 00:00:12 516 | regs->psw.addr = VDSO64_SYMBOL(current, restart_syscall); 00:00:12 | ^~~~~~~~~~~~~ 00:00:12 make[4]: *** [scripts/Makefile.build:273: arch/s390/kernel/signal.o] Error 1
Veronika
If not, please let me know.
thanks,
greg k-h
On Thu, Jul 15, 2021 at 02:54:33PM -0500, Justin Forbes wrote:
On Thu, Jul 15, 2021 at 2:38 PM Veronika Kabatova vkabatov@redhat.com wrote:
On Thu, Jul 15, 2021 at 7:32 PM Greg KH greg@kroah.com wrote:
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
Yes. All runs of the queue hit the problem, including the latest b438694730fd. I also ran a test of the second latest completed run with a patch revert and the issue disappeared.
That said, the c139bde0fdca rebase (second latest) introduced an s390x compilation problem that did not happen before. It is also visible with the latest head. I don't know what commit introduced it yet as the run barely finished:
I hit this same failure building in koji. All of the s390 patches are related, and appear to be an incomplete set:
s390-signal-switch-to-using-vdso-for-sigreturn-and-syscall-restart.patch s390-vdso64-add-sigreturn-rt_sigreturn-and-restart_syscall.patch s390-vdso-add-minimal-compat-vdso.patch s390-vdso-always-enable-vdso.patch s390-vdso-rename-vdso64_lbase-to-vdso_lbase.patch
I'm going to drop all of these, they do not seem to work and will wait for a series from the developers to get it right.
thanks,
greg k-h
On Thu, Jul 15, 2021 at 12:31 PM Greg KH greg@kroah.com wrote:
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
If not, please let me know.
Seeing the same issue here, there is nothing new in the tree.
Justin
On Thu, Jul 15, 2021 at 03:30:32PM -0500, Justin Forbes wrote:
On Thu, Jul 15, 2021 at 12:31 PM Greg KH greg@kroah.com wrote:
On Thu, Jul 15, 2021 at 02:51:15PM +0200, Veronika Kabatova wrote:
On Thu, Jul 15, 2021 at 2:50 PM CKI Project cki-project@redhat.com wrote:
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Commit: ee00910f75ff - powerpc/powernv/vas: Release reference to tgid during window closeThe results of these automated tests are provided below.
Overall result: FAILED (see details below) Merge: OK Compile: FAILEDAll kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix...
We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures:
ppc64le: FAILED (see build-ppc64le.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment)Hi, looks to be introduced by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/c...
Are you sure? I fixed a different build bug in that area a few hours ago, if you rebuild the tree it should be resolved.
If not, please let me know.
Seeing the same issue here, there is nothing new in the tree.
Ok, see it now, dropped the offending patch.
thanks,
greg k-h
linux-stable-mirror@lists.linaro.org
-
CKI Project -
Greg KH -
Justin Forbes -
Veronika Kabatova