All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhao <forrest.zhao@intel.com>
To: "Artem B. Bityuckiy" <dedekind@yandex.ru>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: jffs2 corrupt rarely, how to fix it?
Date: Thu, 16 Jun 2005 17:11:33 +0800	[thread overview]
Message-ID: <42B14245.7070500@intel.com> (raw)
In-Reply-To: <42B12463.4060106@yandex.ru>

Artem B. Bityuckiy wrote:

> zhao wrote:
>
>> Would you please give me some information about the difference
>> between the JFFS2 in 2.4 kernel and the one in 2.6 kernel?
>
>
> One substantial difference is the absence of the lookup() inode operation
> in <= 2.4.19 kernels.
>
> AFAIK, there are no major problems porting recent MTD trees to "not 
> very ancient" 2.4 kernels, where "not very ancient" is, I presume, > 
> 2.4.20. But I didn't try (thank goodness) :-) People just don't want 
> to deal with old stuff anymore.
>
In fact, we were using JFFS2 on kernel 2.4.10.......
And we encountered some problems(e.g. jffs2 corrupt rarely), it seems 
that I need to
back-port JFFS2 in latest 2.4 kernel(2.4.31, right?) to 2.4.10 :( if 
they are not willing
to upgrade to latest 2.4 kernel in the product.

Thanks,
Forrest

  reply	other threads:[~2005-06-16  9:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8126E4F969BA254AB43EA03C59F44E840263CEAE@pdsmsx404>
2005-06-15  9:21 ` jffs2 corrupt rarely, how to fix it? David Woodhouse
2005-06-16  5:38   ` zhao
2005-06-16  7:04     ` Artem B. Bityuckiy
2005-06-16  9:11       ` zhao [this message]
2005-06-16  9:28         ` Artem B. Bityuckiy
2005-06-16 10:24         ` David Woodhouse
2005-06-16 10:12     ` David Woodhouse
     [not found] <F760B14C9561B941B89469F59BA3A8470A558D56@orsmsx401.amr.corp.intel.com>
2005-06-16 18:06 ` David Woodhouse
     [not found] <8126E4F969BA254AB43EA03C59F44E840263CED0@pdsmsx404>
2005-06-15 10:18 ` David Woodhouse
2005-06-10  2:23 tong changda
2005-06-10  8:03 ` Artem B. Bityuckiy
2005-06-10  8:14   ` Munira Ahmed
2005-06-10  8:24     ` Artem B. Bityuckiy
2005-06-10 11:21     ` Jörn Engel
2005-06-13  2:23       ` tong changda
2005-06-13  7:27         ` Jörn Engel
2005-06-14  0:44           ` tong changda
2005-06-14  9:29             ` Jörn Engel
2005-06-14 10:01               ` Munira Ahmed
2005-06-14 13:19                 ` David Woodhouse
     [not found]               ` <1118743045.20555.16.camel@server21>
     [not found]                 ` <20050614101107.GC2354@wohnheim.fh-wedel.de>
2005-06-15  2:25                   ` Munira Ahmed
2005-06-15  6:01                     ` Thomas Gleixner
2005-06-15  8:33                     ` Jörn Engel
2005-06-15  8:45                     ` David Woodhouse
2005-06-15  8:55                       ` Munira Ahmed
2005-06-15  9:02                         ` David Woodhouse
2005-06-15  9:04                           ` Munira Ahmed

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=42B14245.7070500@intel.com \
    --to=forrest.zhao@intel.com \
    --cc=dedekind@yandex.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.