linux-kernel - Re: linux-next: build failure after merge of the kunit-next tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABVgOSksaxKbiBz3Va5FLqAzoHXs4RGkC9YXE=5DmGWzLYU=pw@mail.gmail.com>
Date: Wed, 27 Aug 2025 14:37:39 +0800
From: David Gow <davidgow@...gle.com>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Marie Zhussupova <marievic@...gle.com>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	KUnit Development <kunit-dev@...glegroups.com>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the kunit-next tree

On Wed, 27 Aug 2025 at 13:49, Shuah Khan <skhan@...uxfoundation.org> wrote:
>
> On 8/26/25 03:24, David Gow wrote:
> > On Tue, 26 Aug 2025 at 10:15, Shuah Khan <skhan@...uxfoundation.org> wrote:
> >>
> >> On 8/19/25 01:44, David Gow wrote:
> >>> On Tue, 19 Aug 2025 at 00:32, Shuah Khan <skhan@...uxfoundation.org> wrote:
> >>>>
> >>>> On 8/17/25 20:08, Stephen Rothwell wrote:
> >>>>> Hi all,
> >>>>>
> >>>>> After merging the kunit-next tree, today's linux-next build (x86_64
> >>>>> allmodconfig) failed like this:
> >>>>
> >>>> Thank you Stephen. I did a allmodconfig build on 6.17-rc1 base - didn't
> >>>> see the error.
> >>>>
> >>>> Marie, David, can you take a look this. Looks like conflict with drm
> >>>> in next?
> >>>>
> >>>
> >>> Thanks, Shuah. I've managed to reproduce this with:
> >>> ./tools/testing/kunit/kunit.py run --arch x86_64 --kunitconfig
> >>> drivers/gpu/drm/xe
> >>>
> >>> These patches fix it (and a corresponding drm/xe test failure):
> >>> https://lore.kernel.org/linux-next/20250819073434.1411114-1-davidgow@google.com/T/#t
> >>>
> >>> Ideally, they'll be squashed into the corresponding patches, as
> >>> otherwise there'd be some temporary breakage during bisections. I can
> >>> squash these into the original series and re-send it out if that works
> >>> best for you.
> >>>
> >>
> >> David,
> >>
> >> Please squash them and resend - also I see a kernel test robot
> >> error in patch 1/2.
> >>
> >> I was going to squash them, but I saw the kernel test robot error patch.
> >>
> >
> > Thanks, Shuah.
> >
> > A v2 of the fix series, with the kernel test robot error fixed, is
> > here: https://lore.kernel.org/linux-kselftest/20250821135447.1618942-1-davidgow@google.com/
> >
> > I've also squashed the fixes into a v4 of the original series here:
> > https://lore.kernel.org/linux-kselftest/20250826091341.1427123-1-davidgow@google.com/
> >
>
> I applied these to kunit next and ran test:
>
> ./tools/testing/kunit/kunit.py run --arch x86_64 --kunitconfig drivers/gpu/drm/xe
>
> Looks good. Hopefully next is happy now.

Thanks very much -- this is still passing all of my KUnit test runs
(save for a couple of preexisting genirq-related test failures on some
architectures, for which there are already patches en-route to the irq
folks).

-- David

Download attachment "smime.p7s" of type "application/pkcs7-signature" (5281 bytes)