linux-kernel - Re: Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re: [discuss] [PATCH] Fix triplefault on x86-64 bootup

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: <20070812154623.6000ae68@localhost>
Date:	Sun, 12 Aug 2007 15:46:23 +0200
From:	Paolo Ornati <ornati@...twebnet.it>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Petr Vandrovec <petr@...drovec.name>, discuss@...-64.org,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Please remove ab144f5ec64c42218a555ec1dbde6b60cf2982d6 was Re:
 [discuss] [PATCH] Fix triplefault on x86-64 bootup

On 12 Aug 2007 15:55:50 +0200
Andi Kleen <andi@...stfloor.org> wrote:

> > > Ok Linus already applied your patch. Even though it's a really bad
> > > fragile hack, not better than the old bug.
> > > Petr are you double sure you really tested with
> > > ab144f5ec64c42218a555ec1dbde6b60cf2982d6
> > > already applied? I bet not -- it is the symptom exactly fixed by this patch  
> > 
> > I'm quite sure that this patch is in my tree, as I have that "u8
> > *instr = a->instr;" in apply_alternatives, and it seems that this one
> > was added by checkin you mention...  My tree was synced up to:  
> 
> Can you double check? I have a hard time believing it.

I've seen the reboot too, with "rc2-g3864e8cc" that is newer than
ab144f5ec64c4:

	$ git-log ab144f5ec64c4..| grep 3864e8cc
	commit 3864e8ccbba1dcdea87398ab80fdc8ae0fab7c45

-- 
	Paolo Ornati
	Linux 2.6.23-rc2-gac078602 on x86_64
-
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/