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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080114170856.GA18412@one.firstfloor.org>
Date:	Mon, 14 Jan 2008 18:08:56 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andi Kleen <andi@...stfloor.org>, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: unify pagetable accessors patch causes double fault II

> would be nice to have some debugging apparatus for bugs like this. 
> Perhaps artificially add a large pfn, then convert/unconvert, then 
> subtract it and expect the whole transformation to be an identity 
> mapping? This way we could simulate most of the effects of >4GB RAM, 
> right?

If you want to really test it regularly hacking KVM or Xen or Qemu 
to supply large virtual addresses is probably better. Long ago we
tested with a special BIOS that always put some memory high up
the map.

But then Addresses >3GB are pretty common now because a lot of people put in
2 2 GB DIMMs into systems (2GB DIMMs are not really that expensive anymore). 
And with memory hole remapping you get suitable large addresses then. So
it should be tested often enough.

On the other hand the whole area was always subtly broken. I yesterday 
finally tracked down 

ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/pgtable-nx

which was broken forever. What an embarassing bug :/

-Andi

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