linux-kernel - Re: [PATCH] x86: fix typo(?) in step.c

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: <20080306131323.GD21359@elte.hu>
Date:	Thu, 6 Mar 2008 14:13:23 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Roland McGrath <roland@...hat.com>
Cc:	Jan Beulich <jbeulich@...ell.com>, tglx@...utronix.de,
	hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: fix typo(?) in step.c


* Roland McGrath <roland@...hat.com> wrote:

> > So in theory the bug should manifest itself as block-step mode never 
> > clearing itself, once activated.
> 
> That doesn't happen in the trivial sense of "never", because in the 
> normal case an actual block-step exception happens and that makes the 
> hardware clear BTF from the MSR (as well as TF from eflags).  So it 
> would only come up in a more obscure case. [...]

ah, i missed that detail - this indeed makes this code a lot less 
dangerous.

/me stops worrying

	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/