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: <49BE8A4D.7040204@goop.org>
Date:	Mon, 16 Mar 2009 10:20:13 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [crash] Re: Latest brk patchset

Yinghai Lu wrote:
> Jeremy Fitzhardinge wrote:
>   
>> 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?
>>
>>     
>
> could be max_pfn_mapped change in head_32.S that reduce mapping range to _end only.
>   

Oh, you mean rather than including all low memory?  Possible.  I can 
reproduce it now, so I should be able to sort it out now.

    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/