From: "matsunaga" <matsunaga_kazuhisa@yahoo.co.jp>
To: <tglx@linutronix.de>, <csperandeo@intrinsyc.com>,
<linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 on NAND reboot problems
Date: Tue, 22 Apr 2003 01:08:23 +0900 [thread overview]
Message-ID: <001501c30820$3be142e0$a10486da@w0a3t0> (raw)
In-Reply-To: 200304172105.05365.tglx@linutronix.de
> On Thursday 17 April 2003 18:17, matsunaga wrote:
> > It seems to me that the system was rebooted without wbuf flush.
> > If it is true, another problem I think is that mount process cannot detect
> > the inode inconsistency. This fs should be designed on the premise that
> > power failure happens. The last accessing file do not need to be saved, but
> > fs does.
> > Sorry if this is solved on the latest code
>
> It is designed this way. But we are neither perfect nor can we predict every
> 10e12 possibilities to produce a hidden bug.
>
> I cannot reproduce it here.
> That's why I asked for a bainary Image of the flash content, but I received
> none until now.
To tell the truth, I saw the same BUG() last month, but I had other things to fix and put it aside.
Now it is hard for me to reproduce it, too. I might be solved on the updated code.
Sending binary image could reveal confidential information, so he might hesitate to do it...
> We can only solve problems, which are either reproducable or which can be
> reproduced by some user supplied pattern / image.
>
> We all do our very best to make this code stable and reliable, but we need the
> help from _USERS_ to detect insufficiencies. That's the way open source
> software works. If we don't get the requested feedback / help we can only
> say: You got the code. Feel free to fix it.
I understand. We are all users and not guests.
P.S.
It is trivial, but I think gc.c line 125 ic is not necessary, or the name be changed.
__________________________________________________
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
next prev parent reply other threads:[~2003-04-21 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 19:26 JFFS2 on NAND reboot problems Chris Sperandeo
2003-04-10 21:43 ` Thomas Gleixner
2003-04-17 16:17 ` matsunaga
2003-04-17 19:05 ` Thomas Gleixner
2003-04-21 16:08 ` matsunaga [this message]
[not found] <AEB09EDA2548094C81ED6AA93269F63D01D0520A@siebe001.apac.nokia.com>
2003-04-19 15:58 ` Thomas Gleixner
2003-04-29 15:04 ` Thomas Gleixner
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='001501c30820$3be142e0$a10486da@w0a3t0' \
--to=matsunaga_kazuhisa@yahoo.co.jp \
--cc=csperandeo@intrinsyc.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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