From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: crashme fault
Date: Sun, 16 Sep 2007 05:10:14 +0200 [thread overview]
Message-ID: <20070916031014.GD14501@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0709151542340.16478@woody.linux-foundation.org>
On Sat, Sep 15, 2007 at 03:47:19PM -0700, Linus Torvalds wrote:
>
>
> 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
LTP (http://ltp.sourceforge.net) should have a modern crashme.
-Andi
next prev parent reply other threads:[~2007-09-16 3:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 5:21 crashme fault Randy Dunlap
2007-09-15 4:28 ` Linus Torvalds
2007-09-15 5:05 ` Randy Dunlap
2007-09-15 5:21 ` Randy Dunlap
2007-09-15 18:34 ` Andi Kleen
2007-09-15 18:40 ` Randy Dunlap
2007-09-15 19:44 ` Linus Torvalds
2007-09-15 19:53 ` Randy Dunlap
2007-09-15 22:15 ` Linus Torvalds
2007-09-15 22:47 ` Linus Torvalds
2007-09-15 23:47 ` Randy Dunlap
2007-09-16 0:34 ` Linus Torvalds
2007-09-16 16:40 ` Randy Dunlap
2007-09-16 17:14 ` Linus Torvalds
2007-09-16 18:12 ` Linus Torvalds
2007-09-17 5:06 ` Randy Dunlap
2007-09-17 5:28 ` Linus Torvalds
2007-09-17 14:29 ` Randy Dunlap
2007-09-17 14:53 ` Linus Torvalds
2007-09-17 20:05 ` Randy Dunlap
2007-09-16 18:28 ` Andi Kleen
2007-09-16 3:10 ` Andi Kleen [this message]
2007-09-16 15:53 ` Andrea Arcangeli
2007-09-16 16:17 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070916031014.GD14501@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox