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]

Message-ID: <alpine.LFD.0.999.0709151542340.16478@woody.linux-foundation.org>
Date:	Sat, 15 Sep 2007 15:47:19 -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 Sat, 15 Sep 2007, Linus Torvalds wrote:
> 
> So regardless of whether we want to trust "user_mode(regs)" more than 
> "error_code & PF_USER", it would definitely be very interesting if you can 
> give a good "this is where it started happening".

Also, can you point to good crashme sources, and give the arguments you 
used to run it when it crashed?

The original gjc crashme doesn't even do a "mprotect(PROT_EXEC)" by 
default (nor does it even compile on a modern unix), so it's not going to 
do anything. I hacked it up, and it appears to work ok for me, but I'm not 
at all confident that I'm even close to recreating what you are doing.

(It probably goes without saying that I've not reproduced the oops on my 
Core 2 Duo. Lots of #GP and #PF errors, but nothing interesting.

		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/