From: "zhao, forrest" <forrest.zhao@intel.com>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 after CVS snapshot 2005/11/13 is broken on nandsim
Date: Wed, 21 Dec 2005 17:16:34 +0800 [thread overview]
Message-ID: <1135156594.29050.10.camel@localhost.localdomain> (raw)
In-Reply-To: <43A6A105.9020407@yandex.ru>
On Mon, 2005-12-19 at 15:01 +0300, Artem B. Bityutskiy wrote:
> zhao, forrest wrote:
> > Hi, Artem
> >
> > The following is what I do in my lab:
> > 1 download MTD snapshot of 2005/10/30(the
> > snapshot before I check in EBH patch)
> Thanks, I know that it worked before EBH. Could you please take the
> *lates* CVS stanpshot. Try this on nandsim.
>
Today I did the regression test on kernel 2.6.15-rc5 again,
the result is the same as the one on kernel 2.6.12.2.
The test steps are:
1 mount /dev/mtdblock0 to /mnt, which is a nandsim partition
2 copy a small file(2755 bytes) to /mnt
3 umount /mnt
4 mount /dev/mtdblock0 again
The CVS snapshot before 2005/11/13 is good; the snapshot after
2005/11/13 is broken. I checked in EBH patch on 2005/11/04, so
this is not a bug in EBH. Anyway I'll take look at the diff
between 2005/11/12 and 2005/11/13 to find the bug out.
For snapshot before 2005/11/13, I also did some stress test
on /mnt, it works very well.
For snapshot after 2005/11/13, kernel panic can be easily
reproduced by copying a small file.
Thanks,
Forrest
prev parent reply other threads:[~2005-12-21 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-11 14:12 EBH question 1 Artem B. Bityutskiy
2005-12-12 6:07 ` zhao, forrest
2005-12-12 10:30 ` Artem B. Bityutskiy
2005-12-13 6:26 ` zhao, forrest
2005-12-13 6:51 ` zhao, forrest
2005-12-13 11:47 ` Jarkko Lavinen
[not found] ` <1134545396.27194.11.camel@localhost.localdomain>
2005-12-14 6:42 ` JFFS2 CVS broken after 2005/11/14 Artem Bityutskiy
2005-12-14 8:30 ` zhao, forrest
2005-12-19 12:01 ` EBH question 1 Artem B. Bityutskiy
2005-12-21 6:49 ` zhao, forrest
2005-12-21 9:16 ` zhao, forrest [this message]
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=1135156594.29050.10.camel@localhost.localdomain \
--to=forrest.zhao@intel.com \
--cc=dedekind@yandex.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox