All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Matthieu CASTET <matthieu.castet@parrot.com>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: RFC : attach ubi in readonly mode
Date: Fri, 03 Feb 2012 16:09:21 +0200	[thread overview]
Message-ID: <1328278161.13362.23.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4F2BE3C1.8000104@parrot.com>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On Fri, 2012-02-03 at 14:40 +0100, Matthieu CASTET wrote:
> Hi,
> 
> it could be interesting to attach ubi in read-only mode (for example getting ubi
> volume info without altering flash).
> 
> A solution to do that could be to add an argument to UBI_IOCATT ioctl.

No objections in general, especially if you also:

1. amend the mtd-utils and add support for this option
2. add a piece of doc for the mtd web site
3. add a test for this feature to mtd-utils.git/tests/ubi-test/
(probably simpler to improve one of the existing tests there)

> Another solution should be to have a way to switch MTD_WRITEABLE flags.

This can be done as well, up to you. But I guess UBI will need changes
anyway to handle gracefully situation like:

1. you have RW partition, do a lot of I/O, then reboot uncleanly, so
that there are many erase operations unfinished

2. You reboot, mark the partition R/O, try to attach it - UBI will
probably anyway try to erase some blocks and get -EFORS, not sure will
it panic or not. Should be tested, but probably not a big deal.

IOW, both approaches should be OK.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-03 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 13:40 RFC : attach ubi in readonly mode Matthieu CASTET
2012-02-03 14:09 ` Artem Bityutskiy [this message]
2012-10-04  0:18 ` Marek Vasut

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=1328278161.13362.23.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.com \
    /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.