From: Mark Jackson <mpfj-list@mimc.co.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: JFFS2 corruption
Date: Wed, 27 Feb 2013 15:12:01 +0000 [thread overview]
Message-ID: <512E2241.9040705@mimc.co.uk> (raw)
In-Reply-To: <20130227101824.6e18ba21fb99070594420f29@canb.auug.org.au>
On 26/02/13 23:18, Stephen Rothwell wrote:
> Hi Mark,
>
> On Tue, 26 Feb 2013 15:50:18 +0000 Mark Jackson <mpfj-list@mimc.co.uk> wrote:
>>
>> Just tested the current next-20130226 on a custom AM335X board, and if I mount
>> our JFFS2 image as read/write, the next reboot shows the image as being corrupt.
>>
>> If I reprogram the jffs2 image into NAND and only mount the volume as read-only,
>> no corruption occurs and the system remains intact.
>>
>> I have also tested:-
>>
>> (a) reprogram ubifs image into nand
>> (b) boot the volume as read-only (corrupt -> no)
>> (c) remount the volume as read/write
>> (d) rebooting the volume as read-only (corrupt -> yes)
>
> Thanks for all the testing. Sam questions as in my other email.
Okay, just tested 3v8 plus:-
https://patchwork.kernel.org/patch/1931251/
https://patchwork.kernel.org/patch/1931221/
https://patchwork.kernel.org/patch/1931201/
and changed drivers/mtd/nand/elm.c, line 388 "ti,am33xx-elm" to "ti,am3352-elm"
This produces an identical corruption.
I have also tested next-20130225 and next-20130227, and both cause the same corruption.
Regards
Mark J.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Jackson <mpfj-list@mimc.co.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-next@vger.kernel.org, linux-mtd@lists.infradead.org,
lkml <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: JFFS2 corruption
Date: Wed, 27 Feb 2013 15:12:01 +0000 [thread overview]
Message-ID: <512E2241.9040705@mimc.co.uk> (raw)
In-Reply-To: <20130227101824.6e18ba21fb99070594420f29@canb.auug.org.au>
On 26/02/13 23:18, Stephen Rothwell wrote:
> Hi Mark,
>
> On Tue, 26 Feb 2013 15:50:18 +0000 Mark Jackson <mpfj-list@mimc.co.uk> wrote:
>>
>> Just tested the current next-20130226 on a custom AM335X board, and if I mount
>> our JFFS2 image as read/write, the next reboot shows the image as being corrupt.
>>
>> If I reprogram the jffs2 image into NAND and only mount the volume as read-only,
>> no corruption occurs and the system remains intact.
>>
>> I have also tested:-
>>
>> (a) reprogram ubifs image into nand
>> (b) boot the volume as read-only (corrupt -> no)
>> (c) remount the volume as read/write
>> (d) rebooting the volume as read-only (corrupt -> yes)
>
> Thanks for all the testing. Sam questions as in my other email.
Okay, just tested 3v8 plus:-
https://patchwork.kernel.org/patch/1931251/
https://patchwork.kernel.org/patch/1931221/
https://patchwork.kernel.org/patch/1931201/
and changed drivers/mtd/nand/elm.c, line 388 "ti,am33xx-elm" to "ti,am3352-elm"
This produces an identical corruption.
I have also tested next-20130225 and next-20130227, and both cause the same corruption.
Regards
Mark J.
next prev parent reply other threads:[~2013-02-27 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:50 linux-next: JFFS2 corruption Mark Jackson
2013-02-26 15:50 ` Mark Jackson
2013-02-26 23:18 ` Stephen Rothwell
2013-02-26 23:18 ` Stephen Rothwell
2013-02-27 15:12 ` Mark Jackson [this message]
2013-02-27 15:12 ` Mark Jackson
2013-02-28 4:11 ` Philip, Avinash
2013-02-28 4:11 ` Philip, Avinash
2013-02-28 9:23 ` Mark Jackson
2013-02-28 9:23 ` Mark Jackson
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=512E2241.9040705@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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.