linux-kernel - Re: crashme fault

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:	Sun, 16 Sep 2007 10:14:46 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
cc:	Andi Kleen <andi@...stfloor.org>,
	lkml <linux-kernel@...r.kernel.org>, Andi Kleen <ak@...e.de>
Subject: Re: crashme fault

On Sun, 16 Sep 2007, Randy Dunlap wrote:
> 
> I'll apply this patch today, but I haven't done so yet (for the 2
> bug reports below).

Actually, it's probably better that you don't change your situation 
unnecessarily, in case the bug goes away.

Since you are triggering the problem even *without* the patch, whatever 
crashme is doing now for you is the interesting case.

I suspect NX just isn't active for you, so the mprotect doesn't matter, 
but if it *does* matter, that's interesting in itself.

> Then I'll back up more, prior to 2.6.22 (which got the Huh? message and 
> kept going).

Ahh, ok, so this is not a new thing, and it happened in 2.6.22 too.

I'm really starting to suspect some early EM64T bug, and I also suspect 
that it's harmless but that we should just do the trivial patch to say "if 
the register state is in user mode, we don't care if the CPU says it was a 
kernel access".

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