linux-kernel - Re: [PATCH 1/2] x86: add max

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, 24 May 2012 13:19:48 +0800
From:	Wen Congyang <wency@...fujitsu.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
CC:	rob@...dley.net, tglx@...utronix.de,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] x86: add max_addr boot option

At 05/23/2012 10:25 PM, Bjorn Helgaas Wrote:
> On Tue, May 22, 2012 at 1:02 AM, Wen Congyang <wency@...fujitsu.com> wrote:
> 
>> +       if (start >= max_addr) {
>> +               printk(KERN_INFO "Ingoring memory: %016Lx - %016Lx\n",
>> +                      (unsigned long long)start,
>> +                      (unsigned long long)(start + size));
>> +               return;
>> +       }
>> +
>> +       if (max_addr - start < size) {
>> +               printk(KERN_INFO "Ingoring memory: %016Lx - %016Lx\n",
>> +                      (unsigned long long)max_addr,
>> +                      (unsigned long long)(start + size));
>> +               size = max_addr - start;
> 
> s/Ingoring/Ignoring/
> 
> Please use a format like "e820: ignoring [mem %#010Lx-%#010Lx]" so it
> matches other places where we print physical address ranges.  See
> https://lkml.org/lkml/2012/2/13/436

Hmm, no one reviews/acks patch. So I am not sure whether we need to do this.
So I think there is no need to use such format now.

Thanks
Wen Congyang
> 
> Bjorn
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/