LKML Archive on
help / color / mirror / Atom feed
From: Dave Kleikamp <>
To: Chris Stromsoe <>
Cc: linux-kernel <>,
	Marcelo Tosatti <>
Subject: Re: oops, 2.4.26 and jfs
Date: Fri, 28 May 2004 15:31:33 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 2004-05-28 at 15:15, Chris Stromsoe wrote:
> This morning during a cron run while doing a find across /, I got the
> following oops.

The oops is fixed in 2.4.27-pre3 with the patch:

jfs still may give you problems if 0-order allocations are failing, but
it's not supposed to trap.

David Kleikamp
IBM Linux Technology Center

  reply	other threads:[~2004-05-28 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 20:15 oops, 2.4.26 and jfs Chris Stromsoe
2004-05-28 20:31 ` Dave Kleikamp [this message]
2004-05-29  1:16   ` Chris Stromsoe
2004-05-29  2:32     ` Chris Stromsoe
2004-05-30 17:38     ` Marcelo Tosatti
2004-05-31 11:19       ` Chris Stromsoe
2004-05-31 14:05         ` Marcelo Tosatti

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).