[RFC/PATCH v2] ubi: Add ubiblock read-write driver

[Mike Frysinger]

On Friday 19 April 2013 03:10:23 Gupta, Pekon wrote:
> > On Thursday 18 April 2013 20:13:00 Ezequiel Garcia wrote:
> > > On Thu, Apr 18, 2013 at 04:30:55PM -0400, Mike Frysinger wrote:
> > > > i wonder if the write support should be put behind a CONFIG option.
> > > > personally, the write support is kind of neat and semi-useful for
> > > > development, but i don't plan on shipping anything on that :).  i
> > > > just want read-only support to load an ext2 fs on top of UBI.
> > > 
> > > Mmm... good input. Maybe putting write support behind a CONFIG
> > > and showing a big fat warning when the module loads will do?
> > > (something to prevent regular users from using this carelessly).
> 
> [Pekon]: Permanent disabling of WRITE(s) may not be good approach.
> As it constrains you from updating on-field device remotely, especially
> when your boot-loaders are not in your control.

err, no it doesn't.  we're talking about write support at the UBI *block* 
layer.  nothing is stopping you from writing to the UBI volume directly like 
normal (e.g. ubiupdatevol/etc...).

the reason we're talking about not allowing write support at the *block* layer 
is because it's questionable how many people actually want this, the 
performance isn't good (compared to native flash filesystems), and because the 
write/wear characteristics are unknown.

> [Pekon]: Other options for S/W driven Write-access-control are:

hence, these are all unrelated issues.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20130419/c4770648/attachment.sig>