From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.27: JFS oops
Date: Tue, 30 Jul 2002 07:38:49 -0500 [thread overview]
Message-ID: <200207300738.50302.shaggy@austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207291927160.19349-100000@dad.molina>
On Monday 29 July 2002 19:33, Thomas Molina wrote:
> On Mon, 29 Jul 2002, Dave Kleikamp wrote:
> > On Monday 29 July 2002 10:06, Axel Siebenwirth wrote:
> > I haven't seen this trap before. I'll take a closer look at it,
> > and let you know what I find.
> >
> > > Can I use jfs from cvs with current kernels
> > > (2.5.29/2.4.19-rc3-ac3) to see how latest changes work?
> >
> > Yes. You should be able to just replace everything under fs/jfs
> > with what's in cvs.
>
> Are you saying jfs in 2.5.29 jfs is not a problem? I'm looking to
> see if I should put it on my problem status report.
2.5.29 had a problem that is fixed in Linus's bk tree. I had posted a
patch to this list as well. (Simply remove the calls to d_delete from
namei.c.)
Axel is seeing traps that I haven't seen elsewhere, so that's another
potential problem. We don't know the cause of that one yet.
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2002-07-30 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 15:06 Axel Siebenwirth
2002-07-29 21:43 ` Dave Kleikamp
2002-07-29 21:52 ` Message Signalled Interrupt Imran Badr
2002-07-30 0:33 ` 2.5.27: JFS oops Thomas Molina
2002-07-30 12:38 ` Dave Kleikamp [this message]
2002-07-30 22:38 ` Thomas Molina
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=200207300738.50302.shaggy@austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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
all inboxes | Powered by JetHome®