All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Andrew Murray <amurray@embedded-bits.co.uk>,
	linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: UBI_READWRITE constraint when opening volumes to rename
Date: Mon, 20 Oct 2014 16:10:20 +0300	[thread overview]
Message-ID: <1413810620.7906.267.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <54450352.6000408@nod.at>

On Mon, 2014-10-20 at 14:42 +0200, Richard Weinberger wrote:
> BTW: one corner case is the volume delete operation.
> It touches meta data and LEBs. Currently you need exclusive mode for this.
> IMHO it makes sense to deny metaonly mode if an UBI volume is opened in exclusive mode.

Oh, yes, the 'delete' semantics is that volume goes away and all the
space it had reserved becomes available, so the data it contained is
thrown away, so the operation does affect the data.

Artem.

  reply	other threads:[~2014-10-20 13:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 14:31 UBI_READWRITE constraint when opening volumes to rename Andrew Murray
2014-10-07 14:49 ` Ezequiel Garcia
2014-10-09 10:25 ` Ezequiel Garcia
2014-10-09 11:03   ` Andrew Murray
2014-10-10 21:09     ` Richard Weinberger
2014-10-19 20:58       ` Andrew Murray
2014-10-20 11:10         ` Richard Weinberger
2014-10-20 11:40           ` Andrew Murray
2014-10-20 12:02           ` Artem Bityutskiy
2014-10-20 12:42             ` Richard Weinberger
2014-10-20 13:10               ` Artem Bityutskiy [this message]
2015-06-24 12:27               ` ir. Tjeerd Pinkert
2015-06-25  7:52                 ` Richard Weinberger
2015-06-25  9:28                   ` ir. Tjeerd Pinkert

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=1413810620.7906.267.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=amurray@embedded-bits.co.uk \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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.