linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs : corruption after power cut test
Date: Tue, 13 Jul 2010 14:06:41 +0200	[thread overview]
Message-ID: <4C3C56D1.7060201@parrot.com> (raw)
In-Reply-To: <1279019274.31639.39.camel@localhost>

Hi,

Artem Bityutskiy a écrit :
> Hi,
>> [1]
>> UBIFS: mark VFS SB RO too
>> UBI: init even if MTD device cannot be attached, if built into kernel
>> UBI: remove reboot notifier
>> random: Remove unused inode variable
>> random: drop weird m_time/a_time manipulation
>> UBI: add write checking
>> UBI: simplify debugging return codes
>> UBI: fix attaching error path
>> UBI: support attaching by MTD character device name
>> UBI: mark few variables as __initdata
>> UBI: fix volume creation input checking
>> UBI: fix memory leak in update path
>> UBI: add more checks to chdev open
>> UBI: initialise update marker
>> UBIFS: support mounting of UBI volume character devices
>> UBI: Add ubi_open_volume_path
> 
> You also wan this (new) patch I think:
> http://git.infradead.org/ubifs-2.6.git/commit/6fb4374f6b1b3932f3acfe9d353568d3d8599cad
> 
Yes I managed to trigger this case :)
I also taken 
http://git.infradead.org/ubifs-2.6.git/commitdiff/276de5d2a18bcdc69e6d48a4d96afc14cfef9dcb


Thanks,

Matthieu

  reply	other threads:[~2010-07-13 12:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 12:04 ubifs : corruption after power cut test Matthieu CASTET
2010-07-13  7:27 ` Matthieu CASTET
2010-07-13  8:43   ` Matthieu CASTET
2010-07-13  9:24     ` Matthieu CASTET
2010-07-13 14:24       ` Artem Bityutskiy
2010-07-13 15:10         ` Matthieu CASTET
2010-07-28  7:40           ` Matthieu CASTET
2010-08-02  9:32             ` Matthieu CASTET
2010-08-04 16:14               ` Artem Bityutskiy
2010-08-22  7:44             ` Artem Bityutskiy
2010-09-06  8:55               ` Artem Bityutskiy
2010-09-09  9:22                 ` Matthieu CASTET
2010-09-09  9:51                   ` Artem Bityutskiy
2010-09-24 15:31               ` Matthieu CASTET
2010-09-24 16:50                 ` Artem Bityutskiy
2010-07-13 11:07 ` Artem Bityutskiy
2010-07-13 12:06   ` Matthieu CASTET [this message]
2010-07-13 14:13     ` Artem Bityutskiy
2010-07-13 14:33     ` Artem Bityutskiy

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=4C3C56D1.7060201@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=dedekind1@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).