From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: Randolph Chung <tausq@debian.org>,
PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can]
Date: Fri, 01 Jul 2005 14:07:24 -0400 [thread overview]
Message-ID: <1120241244.5046.16.camel@mulgrave> (raw)
In-Reply-To: <20050701175316.GS5269@systemhalted.org>
On Fri, 2005-07-01 at 13:53 -0400, Carlos O'Donell wrote:
> journal_alloc_journal_head() can return a null pointer causing
> the kernel to die in memset. I think the fix is to skip calling
> memset when new_jh is null. The rest of the code looks ok except
> for possibly
That's true (and needs fixing), but isn't what happened in this case.
Look at the traceback:
> Kernel Fault: Code=15 regs=3249c840 (Addr=73c9d7ba)
The address wasn't NULL, it was something really strange above the
addressable virtual memory in the system.
This fault is consistent with a class of faults we've been seeing since
2.6.11-rc1-pa0 where kmem_cache_alloc() is returning memory that can't
be written to (usually just slightly above the end of virtual memory).
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-01 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 17:53 [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can] Carlos O'Donell
2005-07-01 18:07 ` James Bottomley [this message]
2005-07-01 18:38 ` [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the John David Anglin
2005-07-01 19:08 ` Carlos O'Donell
2005-07-01 19:12 ` Carlos O'Donell
2005-07-01 19:47 ` Carlos O'Donell
2005-07-01 19:05 ` [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can] Carlos O'Donell
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=1120241244.5046.16.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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