linux-kernel - Re: Config NO_BOOTMEM breaks my amd64 box

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:	Thu, 8 Apr 2010 09:27:31 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai <yinghai.lu@...cle.com>
Cc:	James Morris <jmorris@...ei.org>, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org, airlied@...ux.ie,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: Config NO_BOOTMEM breaks my amd64 box


* Yinghai <yinghai.lu@...cle.com> wrote:

> On 04/07/2010 11:32 PM, Ingo Molnar wrote:
> > 
> > * Ingo Molnar <mingo@...e.hu> wrote:
> > 
> >> * James Morris <jmorris@...ei.org> wrote:
> >>
> >>> On Wed, 31 Mar 2010, H. Peter Anvin wrote:
> >>>
> >>>> On 03/31/2010 04:43 PM, James Morris wrote:
> >>>>>>
> >>>>>> Upgraded how?  The problem no longer happens?
> >>>>>
> >>>>> Upgraded to the latest rawhide userland -- I have not since tested with 
> >>>>> bootmem off.  I'll try and do so again when I get a chance.
> >>>>>
> >>>>
> >>>> That would be great.  The sooner the better, obviously.
> >>>
> >>> I'm not seeing any problems now, with current Linus and rawhide.  I'll leave 
> >>> bootmem off and see if anything comes up again.
> >>
> >> (a current bootlog would still be nice)
> >>
> >> Dave, can you reproduce any of these problems with Linus's latest?
> > 
> > ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not 
> > then it probably means that the bug you triggered was already fixed at the 
> > time you reported it, as hpa suspected.)
> 
> James already reported -rc3 fix the problem for him.
> 
> Dave implied -rc3 fixed problem for him

Hm, i'm confused, does this mean that it was all fixed upstream already when 
Dave and James sent their complaints?

Would be nice to have a confirmation from Dave for that (beyond 'implying' 
it), to not keep this thread open-ended.

Thanks,

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