Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Roy Keene <parisc@rkeene.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Kernel 2.4 bug (fwd)
Date: Tue, 20 Apr 2004 12:41:28 +0100	[thread overview]
Message-ID: <20040420114128.GE18329@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0404200039410.31608@hammer.oc9.org>

On Tue, Apr 20, 2004 at 12:41:23AM -0500, Roy Keene wrote:
> Btw, `submit@bugs.parisc-linux.org' doesn't work.

Where do you see that email address still?  It should have been removed ...

> (double free() shouldn't cause the kernel to give page faults, running it
>  enough times eventually crashes the kernel)

What you see there is debug information to help you diagnose your app's
breakage ;-).  You can turn it off by changing #define PRINT_USER_FAULTS
to #undef PRINT_USER_FAULTS in arch/parisc/mm/fault.c.  I believe the
Debian kernel does this by default.

Eventually crashinig the kernel is a different matter.  Can you provide
more information about this?

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  parent reply	other threads:[~2004-04-20 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-20  5:41 [parisc-linux] Kernel 2.4 bug (fwd) Roy Keene
2004-04-20  5:53 ` Randolph Chung
2004-04-20  5:56   ` Roy Keene
2004-04-20  6:06     ` Randolph Chung
2004-04-20 11:41 ` Matthew Wilcox [this message]
2004-04-20 12:48   ` Roy Keene
2004-04-23  6:36     ` Grant Grundler

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=20040420114128.GE18329@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=parisc@rkeene.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