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] [day] [month] [year] [list]

Date:   Thu, 28 Sep 2023 08:47:02 +0200
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Stephen Rothwell" <sfr@...b.auug.org.au>,
        "Andrew Morton" <akpm@...ux-foundation.org>
Cc:     "Muhammad Usama Anjum" <usama.anjum@...labora.com>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
        linux-next <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm tree

On Thu, Sep 28, 2023, at 01:22, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> fs/proc/task_mmu.c: In function 'pagemap_scan_pmd_entry':
> fs/proc/task_mmu.c:2153:22: error: implicit declaration of function 
> 'pagemap_scan_is_interesting_page'; did you mean 
> 'pagemap_scan_is_interesting_vma'? 
> [-Werror=implicit-function-declaration]
>  2153 |                 if 
> (!pagemap_scan_is_interesting_page(categories, p))
>       |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>       |                      pagemap_scan_is_interesting_vma
>
> Caused by commit
>
>   825ebc8e4bf9 ("fs/proc/task_mmu: hide unused 
> pagemap_scan_backout_range() function")
>
> I applied the following fix patch.
>
> From: Stephen Rothwell <sfr@...b.auug.org.au>
> Date: Thu, 28 Sep 2023 09:09:26 +1000
> Subject: [PATCH] fix for "fs/proc/task_mmu: hide unused 
> pagemap_scan_backout_range() function"
>
> Signed-off-by: Stephen Rothwell <sfr@...b.auug.org.au>

Thanks for the fix. I don't see what happened exactly,
maybe we had two conflicting workarounds for the same problem
applied. The version in linux-next works for me on the randconfig
builds, so folding your patch on top should be fine.

    Arnd