linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v2] mtd-utils: integck: add support for volume specific power-cut test
Date: Tue, 27 May 2014 15:37:29 +0300	[thread overview]
Message-ID: <1401194249.1304.140.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B401901@post.tritech.se>

On Thu, 2014-05-15 at 08:21 +0000, Mats Kärrman wrote:
> From a3c9a9be5fe136d1a8e1c029a9f8cc3de634afd2 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Mats=20K=C3=A4rrman?= <mats.karrman@tritech.se>
> Date: Thu, 15 May 2014 10:03:56 +0200
> Subject: [PATCH v2] mtd-utils: integck: add support for volume specific power-cut
>  test
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> Problem:
> The current power-cut test requires power-cut emulation to be enabled globally
> (e.g. for all UBIFS volumes) since the power-cut mode is otherwise lost when
> the file-system is re-mounted. However this may lead to some practical
> problems when the root fs of the tested machine is also of the same type.
> 
> Solution:
> Modify the -p option so that it automatically enables power-cut testing
> selectively for the tested filesystem and then re-enables it after every
> re-mount. Enabling is done by writing "1" to the associated control file.
> The file to use is deduced from the mounted device and the assumption that
> debugfs is mounted on /sys/kernel/debug.
> 
> Signed-off-by: Mats Kärrman <mats.karrman@tritech.se>

Mats, firs of all, my apologies for slowness. And my apologies for
leading you to this direction.

But I think I see the problem with this solution now.

The problem is that with this we won't get power cut emulated while you
mount the file system.

Before this change, we could have something like:

1. Working with the FS, power-cut
2. Unmount the FS, start mounting -> power-cut in the middle of mount.

So we could test power cuts while we are in the middle of recovery from
the previous power cuts, in a way "nested" power-cuts.

With your change, we never have them.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2014-05-27 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15  8:21 [PATCH v2] mtd-utils: integck: add support for volume specific power-cut test Mats Kärrman
2014-05-27 12:37 ` Artem Bityutskiy [this message]
2014-05-27 14:15   ` Mats Kärrman
2014-05-27 14:55     ` Artem Bityutskiy
2014-05-28  8:40       ` Mats Kärrman
2014-05-28  9:30         ` Artem Bityutskiy
2014-05-28 10:52           ` Mats Kärrman
2014-05-28 11:04             ` 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=1401194249.1304.140.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=Mats.Karrman@tritech.se \
    --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).