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: <20191023143847.GJ17610@dhcp22.suse.cz>
Date:   Wed, 23 Oct 2019 16:38:47 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     Chen Wandun <chenwandun@...wei.com>
Cc:     akpm@...ux-foundation.org, vbabka@...e.cz, osalvador@...e.de,
        mgorman@...hsingularity.net, rppt@...ux.ibm.com,
        dan.j.williams@...el.com, alexander.h.duyck@...ux.intel.com,
        anshuman.khandual@....com, pavel.tatashin@...rosoft.com,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/page_alloc: fix gcc compile warning

On Wed 23-10-19 21:48:28, Chen Wandun wrote:
> From: Chenwandun <chenwandun@...wei.com>
> 
> mm/page_alloc.o: In function `page_alloc_init_late':
> mm/page_alloc.c:1956: undefined reference to `zone_pcp_update'
> mm/page_alloc.o:(.debug_addr+0x8350): undefined reference to `zone_pcp_update'
> make: *** [vmlinux] Error 1
> 
> zone_pcp_update is defined in CONFIG_MEMORY_HOTPLUG,
> so add ifdef when calling zone_pcp_update.

David has already pointed out that this has been fixed already but let
me note one more thing. This patch is wrong at two levels. The first one
that it simply does a wrong thing. The comment above the code explains
why zone_pcp_update is called and ifdef makes it depend on
MEMORY_HOTPLUG support which has nothing to do with that code.
The second problem and I find it as a reoccuring problem (and that's why
I am writing this reply) that the changelog explains what but it doesn't
say why. It would certainly be unsatisfactory to say "because compiler
complains". So there would have to be a clarification that
zone_pcp_update is only available for CONFIG_MEMORY_HOTPLUG and why the
code only applies to those configuration. That would be much harder to
justify because there is no real connection.

That being said, a proper changelog with a good explanation of what and
why can help to discover a wrong patch early.

> Signed-off-by: Chenwandun <chenwandun@...wei.com>
> ---
>  mm/page_alloc.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index f9488ef..8513150 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1952,8 +1952,10 @@ void __init page_alloc_init_late(void)
>  	 * so the pcpu batch and high limits needs to be updated or the limits
>  	 * will be artificially small.
>  	 */
> +#ifdef CONFIG_MEMORY_HOTPLUG
>  	for_each_populated_zone(zone)
>  		zone_pcp_update(zone);
> +#endif
>  
>  	/*
>  	 * We initialized the rest of the deferred pages.  Permanently disable
> -- 
> 2.7.4

-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ