Re: ❌ FAIL: Test report for kernel 5.13.2 (stable-queue, ee00910f)

[Greg KH <greg@kroah.com>]

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 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=datawarehouse-public/2021/07/15/337656806
> > > > >
> > > > > 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/commit/?h=queue/5.13&id=07d407cc1259634b3334dd47519ecd64e6818617
> > >
> > > 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