From: Carlos O'Donell <carlos@systemhalted.org>
To: parisc-linux@lists.parisc-linux.org
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Randolph Chung <tausq@debian.org>
Subject: [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can]
Date: Fri, 1 Jul 2005 13:53:20 -0400 [thread overview]
Message-ID: <20050701175316.GS5269@systemhalted.org> (raw)
Dave,
Forwarding your valuable comments to the list for analysis :)
c.
----- Forwarded message from John David Anglin <dave@hiauly1.hia.nrc.ca> -----
> > Backtrace:
> > [<101c10a4>] journal_add_journal_head+0xdc/0x13c
I think this is a bug in journal_add_journal_head:
repeat:
if (!buffer_jbd(bh)) {
new_jh = journal_alloc_journal_head();
memset(new_jh, 0, sizeof(*new_jh));
}
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
if (!new_jh) {
jbd_unlock_bh_journal_head(bh);
goto repeat;
}
This might loop forever. So, somebody who knows how this is
supposed to work should look at it.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
----- End forwarded message -----
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next reply other threads:[~2005-07-01 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 17:53 Carlos O'Donell [this message]
2005-07-01 18:07 ` [dave@hiauly1.hia.nrc.ca: Re: [parisc-linux] Why gas kills the hppa-linux kernel and what you can] James Bottomley
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=20050701175316.GS5269@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=James.Bottomley@steeleye.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.