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] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 27 Jun 2007 19:02:35 +0200
From:	Pim Zandbergen <P.Zandbergen@...roscoop.nl>
To:	Jesse Barnes <jesse.barnes@...el.com>
CC:	Mauro Giachero <mauro.giachero@...il.com>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Andi Kleen <andi@...stfloor.org>,
	Justin Piszcz <jpiszcz@...idpixels.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs

Jesse Barnes wrote:

> It looks like end_pfn might be ~0UL now... can you print that out in 
> your configuration?

Er, do you need the value of end_pfn ?
Here's what I changed:

if ((highest_addr >> PAGE_SHIFT) != end_pfn) {
         printk(KERN_WARNING "***************\n");
         printk(KERN_WARNING "**** WARNING: likely BIOS bug\n");
         printk(KERN_WARNING "**** MTRRs don't cover all of "
                "memory, trimmed %lu pages\n", end_pfn -
                (highest_addr >> PAGE_SHIFT));
         printk(KERN_WARNING "**** end_pfn before = %lu\n", end_pfn);
         end_pfn = highest_addr >> PAGE_SHIFT;
         printk(KERN_WARNING "**** end_pfn after = %lu\n", end_pfn);
         printk(KERN_WARNING "***************\n");
}

Here's the result:
***************
**** WARNING: likely BIOS bug
**** MTRRs don't cover all of memory, trimmed 18446744073709486080 pages
**** end_pfn before = 2293760
**** end_pfn after = 2359296
***************

Hope that's what you needed.
Pim

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ