From: "Florian Schaefer" <listbox@netego.de>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: codalist@TELEMANN.coda.cs.cmu.edu, linux-kernel@vger.kernel.org,
ext3-users@redhat.com
Subject: Re: [PATCH] Re: Coda and Ext3
Date: 20 Sep 2001 13:38:26 CET [thread overview]
Message-ID: <200109201238.f8KCcSo00731@dexter.netego.de> (raw)
In-Reply-To: <20010919213713.D8947@cs.cmu.edu>
In-Reply-To: <3B9792FB.7020708@progress.com> <20010906115302.B826@cs.cmu.edu> <1000909441.2017.20.camel@pcsshah> <20010919213713.D8947@cs.cmu.edu>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Wed, 19 Sep 2001 21:37:14 -0400, Jan Harkes said:
>On Wed, Sep 19, 2001 at 10:23:36AM -0400, Sujal Shah wrote:
> > The Linux Coda drivers and the ext3 patches don't seem to get along
> > very well, at least in Linux 2.4.7. I've got a stock 2.4.7 kernel with
>
> The attached patch should fix it. I haven't tested it against ext3, but
> with tmpfs which used to have the same problem, i.e. not using
> generic_file_ functions to access the container files. I'll pass it on
> to Linus and Alan once I get some feedback on whether this solves all
> problems. I believe this will fix the whole batch of problems that are
> have been reported with ext3fs, XFS, and tmpfs.
I just tried your patch together with coda-debug-client-5.3.15-1,
kernel-2.4.9 and ext3-2.4-0.9.6-249 and still get the BUG message. The
ksymoops output is attached.
Ciao
Florian
[-- Attachment #2: BUG.ksymoops --]
[-- Type: application/x-unknown, Size: 9478 bytes --]
next prev parent reply other threads:[~2001-09-20 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010906115302.B826@cs.cmu.edu>
[not found] ` <3B9792FB.7020708@progress.com>
2001-09-19 14:23 ` Sujal Shah
2001-09-19 15:47 ` Jan Harkes
2001-09-20 1:37 ` [PATCH] " Jan Harkes
2001-09-20 12:38 ` Florian Schaefer [this message]
2001-09-20 16:06 ` Jan Harkes
2001-09-20 16:30 ` Florian Schaefer
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=200109201238.f8KCcSo00731@dexter.netego.de \
--to=listbox@netego.de \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=ext3-users@redhat.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome