Linux-mtd Archive on lore.kernel.org
 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: [RFC] mtd-utils: integck: add support for volume specific power-cut test
Date: Mon, 19 Aug 2013 17:55:18 +0300	[thread overview]
Message-ID: <1376924118.2089.482.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1376923842.2089.480.camel@sauron.fi.intel.com>

On Mon, 2013-08-19 at 17:50 +0300, Artem Bityutskiy wrote:
> On Mon, 2013-08-19 at 14:24 +0000, Mats Kärrman wrote:
> > # echo "1" > /sys/kernel/debug/ubifs/ubi1_0/tst_recovery
> > 
> > However, in the latter case, the flag is reset when the file system is
> > remounted
> > so the test continues without tst_recovery enabled.
> 
> Ah, I see it now.
> 
> Did you try if you can resolve the mount path into 'ubiX_Y' in integck,
> so that one wouldn't need to pass this -P <loong/path/string> option?

Check the recover_tested_fs() which uses get_tested_fs_mntent() which
parses /proc/mounts. Can you do a similar thing and find the 'ubiX_Y'
part, and then just write 1 to the sysfs path. -P would not be needed
then at all.

-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2013-08-19 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19  8:50 [RFC] mtd-utils: integck: add support for volume specific power-cut test Mats Kärrman
2013-08-19 13:36 ` Artem Bityutskiy
2013-08-19 14:24   ` Mats Kärrman
2013-08-19 14:50     ` Artem Bityutskiy
2013-08-19 14:55       ` Artem Bityutskiy [this message]
2013-08-19 15:01         ` Mats Kärrman
2013-08-19 15:16           ` Artem Bityutskiy
2013-08-19 15:37             ` Mats Kärrman
2013-08-20 12:23               ` Artem Bityutskiy
2013-08-20 13:10                 ` Artem Bityutskiy
2013-08-21  6:21                   ` Mats Kärrman

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=1376924118.2089.482.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