From: Willy Tarreau <w@1wt.eu>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Benson Young <benson6877@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Gstir <david@sigma-star.at>
Subject: Re: ubiblock RW
Date: Mon, 28 Mar 2016 10:17:55 +0200 [thread overview]
Message-ID: <20160328081755.GA17870@1wt.eu> (raw)
In-Reply-To: <1459148213.19765.14.camel@gmail.com>
On Mon, Mar 28, 2016 at 09:56:53AM +0300, Artem Bityutskiy wrote:
> You can add a per-volume R/O flag if needed, yes. Expose it to user-
> space. This may be a useful thing irrespectively. I am not sure how it
> helps with ubiblock though.
>
> Ideally, the ubiblock R/W enabled flag should be stored in ubiblock,
> not in UBI, not in MTD, because you want ubiblock to have full control
> over it. You do not want a user go and change the flag via the UBI
> interface whenever the user feels like, right?
>
> To have this kind of flag in ubiblock, it needs an on-flash superblock
> or something. If you are not going to introduce it, which I believe is
> the case, then the only option left in my opinion is a ubiblock module
> parameter.
>
> If I am a ubiblock user who needs the write support, and this naive
> write support is good enough for me, I want it enabled by default on my
> product. A module parameter with a sound name like 'dangerous-write-
> support' or something would work fine for me.
Thanks Artem for the explanation. I think it all makes sense indeed.
Willy
prev parent reply other threads:[~2016-03-28 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABJ+KKu2RJuHXE3LpmzSYtE0i57sHDUHWOxPxufCP94RTa=eBA@mail.gmail.com>
2016-03-24 14:23 ` ubiblock RW Ezequiel Garcia
2016-03-24 20:38 ` Richard Weinberger
2016-03-24 21:26 ` Ezequiel Garcia
2016-03-24 21:39 ` Willy Tarreau
2016-03-25 20:28 ` Richard Weinberger
2016-03-25 11:51 ` Artem Bityutskiy
2016-03-25 20:50 ` Ezequiel Garcia
2016-03-25 20:51 ` Ezequiel Garcia
2016-03-25 21:25 ` Richard Weinberger
2016-03-26 6:01 ` Willy Tarreau
2016-03-27 22:01 ` Richard Weinberger
2016-03-28 6:56 ` Artem Bityutskiy
2016-03-28 8:17 ` Willy Tarreau [this message]
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=20160328081755.GA17870@1wt.eu \
--to=w@1wt.eu \
--cc=benson6877@gmail.com \
--cc=david@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox