linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, Heinz.Egger@linutronix.de,
	linux-mtd@lists.infradead.org, tim.bird@am.sony.com,
	tglx@linutronix.de, Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [PATCH] [RFC] UBI: Implement Fastmap support
Date: Thu, 24 May 2012 11:19:52 +0300	[thread overview]
Message-ID: <1337847592.15137.83.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <b3d5919d0b35bb559b7dc115bc9e2720@radon2.swed.at>

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

On Tue, 2012-05-22 at 22:11 +0200, Richard Weinberger wrote:
> >> > In the error case, what are the consequences leaving the older
> on-flash
> >> > fastmap? Shouldn't it be invalidated?
> >>
> 
> After thinking a bit more about this case I think the best we can to
> is
> switching to read-only mode if ubi_update_fastmap()
> fails.
> 
Unless it fails because of -EIO, which means the PEB may become bad and
you need to pick a different one and schedule the faulty one for
torturing and marking as bad.

-- 
Best Regards,
Artem Bityutskiy

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

  reply	other threads:[~2012-05-24  8:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 14:01 [RFC v6] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-21 14:01 ` [PATCH] [RFC] UBI: Implement Fastmap support Richard Weinberger
2012-05-22 13:43   ` Artem Bityutskiy
2012-05-22 15:01   ` Shmulik Ladkani
2012-05-22 16:55     ` Richard Weinberger
2012-05-22 18:18       ` Shmulik Ladkani
2012-05-22 18:57         ` Richard Weinberger
2012-05-23  6:18           ` Shmulik Ladkani
2012-05-23  7:43             ` Richard Weinberger
2012-05-22 20:11         ` Richard Weinberger
2012-05-24  8:19           ` Artem Bityutskiy [this message]
2012-05-24  8:26             ` Richard Weinberger
2012-05-24  9:21               ` Artem Bityutskiy
2012-05-24  8:17       ` Artem Bityutskiy
2012-05-24  9:56         ` Shmulik Ladkani
2012-05-24 10:03           ` Richard Weinberger
2012-05-24 20:07             ` Shmulik Ladkani
2012-05-24  8:22       ` Artem Bityutskiy
2012-05-24  8:24         ` Richard Weinberger
  -- strict thread matches above, loose matches on Subject: below --
2012-05-23 11:06 [RFC v7] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-23 11:06 ` [PATCH] [RFC] UBI: Implement Fastmap support Richard Weinberger
2012-05-26 13:22   ` Artem Bityutskiy
2012-05-31 10:37   ` Adrian Hunter
2012-05-31 13:31     ` Richard Weinberger
2012-06-01  5:47   ` Adrian Hunter
2012-06-01  8:00     ` Richard Weinberger
2012-06-01  8:10       ` Artem Bityutskiy
2012-06-01  8:10         ` Richard Weinberger
2012-06-01  8:47           ` Adrian Hunter

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=1337847592.15137.83.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=Heinz.Egger@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=shmulik.ladkani@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tim.bird@am.sony.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 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).