Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "Greg Lindahl" <lindahl@keyresearch.com>, <linux-mips@linux-mips.org>
Subject: Re: Anyone running crashme?
Date: Fri, 17 Jan 2003 08:41:43 +0100	[thread overview]
Message-ID: <000f01c2bdfb$e2cb7220$10eca8c0@grendel> (raw)
In-Reply-To: 20030117012644.GA2058@wumpus.internal.keyresearch.com

Actiually, we've been using crashme at MIPS
for several years now, both to torture the Linux 
kernel and to push our chip designs into unexpected 
corner cases.  We found a fair number of kernel
bugs, and fixed them in our internal sources
(snapshots are generally available under
ftp://ftp.mips.com/pub/linux/mips/kernel )
and have pushed our fixes out toward the
mainline distributions.  That's not to say that
they all get there.

Two things to watch out for: There is a class
of crashme misbehavior, usually manifest in
forked threads that do not terminate correctly
until the program is shut down, that arises not
from a kernel bug, but from a libc built with
downrev kernel headers.  And if you have a
CPU that supports EJTAG, you either need to
make sure that your boot ROM has code at the
EJTAG debug exception vector that jumps to the
EJTAG kseg0 pseudo-vector used by the Linux
kernel (well, *our* Linux kernel anyway ;-), 
or you need to put a filter in crashme to ensure 
that it does not generate EJTAG debug breakpoint 
instructions.

But I'm glad to see that someone else is using it.

----- Original Message ----- 
From: "Greg Lindahl" <lindahl@keyresearch.com>
To: <linux-mips@linux-mips.org>
Sent: Friday, January 17, 2003 2:26 AM
Subject: Anyone running crashme?


> I've been running crashme a little against Linux mips, and from the
> bugs I immediately found I suspect that no one's been running it.
> Crashme generates random bytes and then executes them, catching the
> resulting signals and generating more random bytes. The random number
> seed is provided by the user, so that problems are repeatable.
> 
> If you like debugging, you can find the source at:
> 
> http://people.delphiforums.com/gjc/crashme.html
> 
> -- greg
> 
> 
> 
> 
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: Greg Lindahl <lindahl@keyresearch.com>, linux-mips@linux-mips.org
Subject: Re: Anyone running crashme?
Date: Fri, 17 Jan 2003 08:41:43 +0100	[thread overview]
Message-ID: <000f01c2bdfb$e2cb7220$10eca8c0@grendel> (raw)
Message-ID: <20030117074143.Kva4NoxidVN4omV8rLIFK-mzBGcjEPJjLxKNT3ctLEQ@z> (raw)
In-Reply-To: 20030117012644.GA2058@wumpus.internal.keyresearch.com

Actiually, we've been using crashme at MIPS
for several years now, both to torture the Linux 
kernel and to push our chip designs into unexpected 
corner cases.  We found a fair number of kernel
bugs, and fixed them in our internal sources
(snapshots are generally available under
ftp://ftp.mips.com/pub/linux/mips/kernel )
and have pushed our fixes out toward the
mainline distributions.  That's not to say that
they all get there.

Two things to watch out for: There is a class
of crashme misbehavior, usually manifest in
forked threads that do not terminate correctly
until the program is shut down, that arises not
from a kernel bug, but from a libc built with
downrev kernel headers.  And if you have a
CPU that supports EJTAG, you either need to
make sure that your boot ROM has code at the
EJTAG debug exception vector that jumps to the
EJTAG kseg0 pseudo-vector used by the Linux
kernel (well, *our* Linux kernel anyway ;-), 
or you need to put a filter in crashme to ensure 
that it does not generate EJTAG debug breakpoint 
instructions.

But I'm glad to see that someone else is using it.

----- Original Message ----- 
From: "Greg Lindahl" <lindahl@keyresearch.com>
To: <linux-mips@linux-mips.org>
Sent: Friday, January 17, 2003 2:26 AM
Subject: Anyone running crashme?


> I've been running crashme a little against Linux mips, and from the
> bugs I immediately found I suspect that no one's been running it.
> Crashme generates random bytes and then executes them, catching the
> resulting signals and generating more random bytes. The random number
> seed is provided by the user, so that problems are repeatable.
> 
> If you like debugging, you can find the source at:
> 
> http://people.delphiforums.com/gjc/crashme.html
> 
> -- greg
> 
> 
> 
> 
> 
> 

  reply	other threads:[~2003-01-17  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17  1:26 Anyone running crashme? Greg Lindahl
2003-01-17  7:41 ` Kevin D. Kissell [this message]
2003-01-17  7:41   ` Kevin D. Kissell
2003-01-20 19:44 ` Jun Sun

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='000f01c2bdfb$e2cb7220$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=lindahl@keyresearch.com \
    --cc=linux-mips@linux-mips.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