public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sébastien Côté" <scote1@Matrox.COM>
To: Alexander Larsson <alex@cendio.se>
Cc: David Woodhouse <dwmw2@infradead.org>, mtd@infradead.org
Subject: Re: MTD CVS update: 'mtd/fs/jffs inode-v22.c Makefile inode.c'
Date: Fri, 16 Jun 2000 10:49:53 -0400	[thread overview]
Message-ID: <394A3E91.4C025831@matrox.com> (raw)
In-Reply-To: Pine.LNX.4.10.10006161601090.32348-100000@tammy.signum.se

Alexander Larsson wrote:

> I did the most obvious conversions, but i had to leave a couple of things
> because that need more thinking and testing:
> 
> jffs_read_super() - Does it really has to lock the superblock here?

Ext2 does it in 2.2 and it seemed right to me.  If the fs changes while
it is being built, this is really not a good thing.
 
> jffs_read_page() - I've done some changes here in the 2.3 version that
> might be intresting to 2.2. These are mainly page handling stuff, you need
> to check that carefully.

I'll have to check what changes you're talking about but IIRC the page
handling changed quite a bit between 2.2 and 2.3.

> jffs_file_write() - The 2.3 version has some file-size handling (SIGXFSZ)
> that could be interesting for 2.2. There is also some semaphore locking
> that 2.2 doesn't have which I'm a bit unsure of if it is needed in 2.2.
> The *pos handling can maybe also be moved over.
> 
> There are also some comments (/* Is this really needed in 2.2?
> */) sprinkled in the code. These are mainly corner-cases which I and al
> viro has removed from the 2.3 code because they are handled by the VFS.
> Probably most of these are handled by the 2.2 VFS too...
>
> Also there are some french comments in the code that i left there, because
> i don't understand them.

Sorry about that.  I completly forgot them when I sent my tree to David
:)

-- 
Sébastien Côté


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-06-16 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-16 11:13 MTD CVS update: 'mtd/fs/jffs inode-v22.c Makefile inode.c' David Woodhouse
2000-06-16 11:42 ` Alexander Larsson
2000-06-16 11:46   ` David Woodhouse
2000-06-16 11:49     ` Alexander Larsson
2000-06-16 12:31       ` David Woodhouse
2000-06-16 12:46         ` Alexander Larsson
2000-06-16 14:13         ` Alexander Larsson
2000-06-16 14:49           ` Sébastien Côté [this message]
2000-06-16 15:48           ` Sébastien Côté
2000-06-16 11:58     ` Alexander Larsson
2000-06-16 12:05       ` David Woodhouse
2000-06-16 12:17         ` Alexander Larsson

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=394A3E91.4C025831@matrox.com \
    --to=scote1@matrox.com \
    --cc=alex@cendio.se \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.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