From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 8 Feb 2014 23:51:49 +0100 From: Willy Tarreau To: Richard Weinberger Subject: Re: [PATCH 1/1] ubi: Introduce block devices for UBI volumes Message-ID: <20140208225149.GA22376@1wt.eu> References: <1391027881-8354-1-git-send-email-ezequiel.garcia@free-electrons.com> <1391027881-8354-2-git-send-email-ezequiel.garcia@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Thomas Petazzoni , Mike Frysinger , Artem Bityutskiy , Michael Opdenacker , "linux-mtd@lists.infradead.org" , Tim Bird , Ezequiel Garcia , Piergiorgio Beruto , Brian Norris , David Woodhouse List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sat, Feb 08, 2014 at 10:37:19PM +0100, Richard Weinberger wrote: > > +config MTD_UBI_BLOCK_WRITE_SUPPORT > > + bool "Enable write support (DANGEROUS)" > > + default n > > + depends on MTD_UBI_BLOCK > > + select MTD_UBI_BLOCK_CACHED > > + help > > + This is a *very* dangerous feature. Using a regular block-oriented > > + filesystem might impact heavily on a flash device wear. > > + Use with extreme caution. > > + > > + If in doubt, say "N". > > I really vote for dropping write support at all. Why ? When you put a read-only filesystem there such as squashfs, the only writes you'll have will be updates, and write support will be the only way to update the filesystem. So removing write support seriously impacts the usefulness of the feature itself. Willy