linux-kernel - Re: linux-next: build failure after merge of the mm 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <16389d71-4a1f-4049-8d81-5814d240c46d@lucifer.local>
Date: Wed, 24 Jul 2024 06:31:53 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm tree

On Wed, Jul 24, 2024 at 08:49:02AM GMT, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from mm/vma.c:7:
> mm/vma_internal.h:46:10: fatal error: asm/page_types.h: No such file or directory
>    46 | #include <asm/page_types.h>
>       |          ^~~~~~~~~~~~~~~~~~
>

This was already fixed with a simple fix-patch that already landed in
mm-unstable. It seems unfortunate timing means that you didn't pull it.

> Caused by commit
>
>   b102945dd5b2 ("mm: move internal core VMA manipulation functions to own file")
>
> from the mm-unstable branch of the mm tree.
>
> asm/page_types.h only exists for x86 ...
>
> I have dropped the mm tree until the end of the merge window.
>

This seems a bit drastic. It's literally caused by 2 unncessary header includes
which are already fixed.

We really want to get some time in -next for this ideally.

> --
> Cheers,
> Stephen Rothwell