Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp788960imm; Wed, 4 Jul 2018 06:05:58 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfYqQIgImgIaMnmds+pLWBkWua4b3+obTDzVPcr+vLBcZObiXhMMfJKS1I7nBLER3EA5KE9 X-Received: by 2002:a62:ff0e:: with SMTP id b14-v6mr2116874pfn.135.1530709558300; Wed, 04 Jul 2018 06:05:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530709558; cv=none; d=google.com; s=arc-20160816; b=O9ZtRIZtUu28LTS2QKTOUsCMYl9228i6N+qmRBeHOiG77lzZy4ohRawwav71hEqybF PGvC8e3QJgiH8su6evB4OfRZ5X97C9m0O9ITu40Gue5rS3kakXjozp5ZCwuNXB2o7n05 1YiWP5VFBqqmEbzTJT7SqVF+w8RJlqS64bcVIcIyG3/tf/ZvhufseOEe9ZhDdPZ/bFjq Vexxshi21T+5qVZ7gXPTADzdeAR7zPxOOSviKGcUAMgTsVOlIq+xWgU0AjNPkItUf/tK q5Kpa3IGqvCaQfwq7QTTTt7AzuguEWcWPC5VYtFyO2z0/3a3fSlT2vboHMvTq0+A0nFH zRAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=HsZ9/6UcNCloNHFDi02vgrn587B/Sdkd1KxgUiLhddo=; b=oi+XwCn+Rzckax5It2g2AyCRAUzb5GZuO+MkYPWrTvSMd1jwRbuO1/CTPyVrpRqxwa I7GmFzRXmyXBIeBiODE1akuKLtIsjyMwGdpCsJTH9jE2svhexRDVdMTxJ3TfRN0HNUSA ghYrmiU9xUmDjSITiz3MOxnpJBO/o/DLVlrBaTLkZTPf/XZDka+SuUOJKomDgePugwXM JVinPmLNmg+pGVVmZiltdfXufi0u3JtNGRv9C+T/ZacXg3mDemw6F8NWqzVAMxXMtnq3 TTpRNVgC4Y3YI3Y92GFtqomOmDE1FjTnx1f3i23zHflZ4eKE5HeYZTTHvxlUvk1BG+9d WeWA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r23-v6si3407989pgb.623.2018.07.04.06.05.43; Wed, 04 Jul 2018 06:05:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753185AbeGDNFE (ORCPT + 99 others); Wed, 4 Jul 2018 09:05:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:51282 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752715AbeGDNFD (ORCPT ); Wed, 4 Jul 2018 09:05:03 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 7CF2FADBA; Wed, 4 Jul 2018 13:05:01 +0000 (UTC) Date: Wed, 4 Jul 2018 15:05:00 +0200 From: Michal Hocko To: Mike Rapoport Cc: Andrew Morton , linux-mm , lkml , Matthew Wilcox Subject: Re: [PATCH] mm/memblock: replace u64 with phys_addr_t where appropriate Message-ID: <20180704130500.GP22503@dhcp22.suse.cz> References: <1530637506-1256-1-git-send-email-rppt@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1530637506-1256-1-git-send-email-rppt@linux.vnet.ibm.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 03-07-18 20:05:06, Mike Rapoport wrote: > Most functions in memblock already use phys_addr_t to represent a physical > address with __memblock_free_late() being an exception. > > This patch replaces u64 with phys_addr_t in __memblock_free_late() and > switches several format strings from %llx to %pa to avoid casting from > phys_addr_t to u64. > > CC: Michal Hocko > CC: Matthew Wilcox > Signed-off-by: Mike Rapoport > --- > mm/memblock.c | 46 +++++++++++++++++++++++----------------------- > 1 file changed, 23 insertions(+), 23 deletions(-) > > diff --git a/mm/memblock.c b/mm/memblock.c > index 03d48d8..20ad8e9 100644 > --- a/mm/memblock.c > +++ b/mm/memblock.c > @@ -330,7 +330,7 @@ static int __init_memblock memblock_double_array(struct memblock_type *type, > { > struct memblock_region *new_array, *old_array; > phys_addr_t old_alloc_size, new_alloc_size; > - phys_addr_t old_size, new_size, addr; > + phys_addr_t old_size, new_size, addr, new_end; > int use_slab = slab_is_available(); > int *in_slab; > > @@ -391,9 +391,9 @@ static int __init_memblock memblock_double_array(struct memblock_type *type, > return -1; > } > > - memblock_dbg("memblock: %s is doubled to %ld at [%#010llx-%#010llx]", > - type->name, type->max * 2, (u64)addr, > - (u64)addr + new_size - 1); > + new_end = addr + new_size - 1; > + memblock_dbg("memblock: %s is doubled to %ld at [%pa-%pa]", > + type->name, type->max * 2, &addr, &new_end); I didn't get to check this carefully but this surely looks suspicious. I am pretty sure you wanted to print the value here rather than address of the local variable, right? -- Michal Hocko SUSE Labs