public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: sujal@sujal.net
Cc: codalist@TELEMANN.coda.cs.cmu.edu, linux-kernel@vger.kernel.org,
	ext3-users@redhat.com
Subject: Re: Coda and Ext3
Date: Wed, 19 Sep 2001 11:47:23 -0400	[thread overview]
Message-ID: <20010919114721.C14151@cs.cmu.edu> (raw)
In-Reply-To: <3B9792FB.7020708@progress.com> <20010906115302.B826@cs.cmu.edu> <1000909441.2017.20.camel@pcsshah>
In-Reply-To: <1000909441.2017.20.camel@pcsshah>

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
> a patch applied to the USB drivers (for a sony digital camera; see
> http://www.sujal.net/tech/linux/ just a change in unusual_devs.h). 
> 
> After I applied the ext3 patches from
> http://www.uow.edu.au/~andrewm/linux/ext3/ .  Basically, when an
> application tries to write to a file system mounted via coda, the
> application terminates with "Memory Fault" returned to the terminal. 
> THe file system still thinks it's busy (can't umount).

Yeah, I know, and it will probably work when you don't enable
data-journalling. Coda's kernelmodule currently uses generic_file_read
and generic_file_write on it's containerfiles, which works for many
filesystems. However, ext3fs (and tmpfs and several others) have a
filesystem specific write implementation and don't really like being
called with the generic functions.

The patch is simple, but I haven't made it yet. Basically we need to
wrap the read/write calls and call cii->c_cfile->f_op->file_write or
something.

> loaded, however.  Also, I backed out the patches for ext3 and the
> problem went away.

ext2 uses the generic file read/write functions, so whenever ext2 is the
underlying filesystem it all works fine.

Jan


  reply	other threads:[~2001-09-19 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B9792FB.7020708@progress.com>
     [not found] ` <20010906115302.B826@cs.cmu.edu>
2001-09-19 14:23   ` Coda and Ext3 Sujal Shah
2001-09-19 15:47     ` Jan Harkes [this message]
2001-09-20  1:37     ` [PATCH] " Jan Harkes
2001-09-20 12:38       ` Florian Schaefer
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=20010919114721.C14151@cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=codalist@TELEMANN.coda.cs.cmu.edu \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sujal@sujal.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