linux-kernel - Re: [crash] Re: Latest brk patchset

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]

Message-ID: <49BE7A84.2030503@goop.org>
Date:	Mon, 16 Mar 2009 09:12:52 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] Re: Latest brk patchset

Ingo Molnar wrote:
>> And the resulting kernel booted fine under qemu with 1Gbyte of 
>> memory.  I'll try on real hardware a bit later, but it doesn't 
>> seem like something that should be affected by qemu vs native, 
>> unless it has something to do with the specific e820 map.
>>     
>
> Note that the crash was reproducible and it very clearly went 
> away when i excluded those commits from tip:master.
>   

Yep, and it looks like the kind of problem those changes might cause.  
But I can't reproduce it, and its not obvious to me what's actually 
going wrong.  Any chance you could bisect the failure down to a specific 
changeset, and print "start", "max_pfn_mapped" and "tables" where it fails?

Thanks,
    J
--
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/