[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8dfaf60-ff35-66d3-7bc1-f11eaaef642a@huawei.com>
Date: Tue, 13 Dec 2022 09:34:24 +0800
From: Kefeng Wang <wangkefeng.wang@...wei.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>
CC: 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-hotfixes tree
Hi, this patch relays on Tony Luck's Patch series "Copy-on-write poison
recovery".[1]
and tested ppc64_defconfig based on next-20221208, it's no build failure
I think it is not very hotfix, also will send v3 to address some comments
we could adjust the patch order in mm tree, thanks.
[1]
https://lore.kernel.org/all/50506c8a-71c1-9c68-aa47-7e8dc68a3c52@huawei.com/
On 2022/12/13 6:30, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mm-hotfixes tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> mm/ksm.c: In function 'ksm_might_need_to_copy':
> mm/ksm.c:2605:21: error: implicit declaration of function 'copy_mc_user_highpage'; did you mean 'copy_user_highpage'? [-Werror=implicit-function-declaration]
> 2605 | if (copy_mc_user_highpage(new_page, page, address, vma)) {
> | ^~~~~~~~~~~~~~~~~~~~~
> | copy_user_highpage
>
> Caused by commit
>
> b7edf4b1cdb1 ("mm: hwpoison: support recovery from ksm_might_need_to_copy()")
>
> I have reverted that commit for today.
>
Powered by blists - more mailing lists