linux-kernel - Re: linux-next: Tree for Mar 11 (vmemmap)

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: <YEqPypUK2hSOYjA7@localhost.localdomain>
Date:   Thu, 11 Mar 2021 22:46:50 +0100
From:   Oscar Salvador <osalvador@...e.de>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux MM <linux-mm@...ck.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: Tree for Mar 11 (vmemmap)

On Thu, Mar 11, 2021 at 10:51:14AM -0800, Randy Dunlap wrote:
> On 3/10/21 9:14 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> > so please be careful if you are trying to bisect a bug.
> > 
> > News: if your -next included tree is based on Linus' tree tag
> > v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
> > consider rebasing it onto v5.12-rc2. Also, please check any branches
> > merged into your branch.
> > 
> > Changes since 20210310:
> > 
> 
> on x86_64:
> 
> ../arch/x86/mm/init_64.c: In function ‘vmemmap_populate_hugepages’:
> ../arch/x86/mm/init_64.c:1585:6: error: implicit declaration of function ‘vmemmap_use_new_sub_pmd’ [-Werror=implicit-function-declaration]
>       vmemmap_use_new_sub_pmd(addr, next);
>       ^~~~~~~~~~~~~~~~~~~~~~~
> ../arch/x86/mm/init_64.c:1591:4: error: implicit declaration of function ‘vmemmap_use_sub_pmd’ [-Werror=implicit-function-declaration]
>     vmemmap_use_sub_pmd(addr, next);
>     ^~~~~~~~~~~~~~~~~~~

It seems that next-20210311 contains v5, which still had this issue.
I sent out v6 yesterday fixing this up [1].

I cannot reproduce with your config there.


[1] https://patchwork.kernel.org/project/linux-mm/cover/20210309214050.4674-1-osalvador@suse.de/

-- 
Oscar Salvador
SUSE L3