lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1283410392.6920.36.camel@wall-e.seibold.net>
Date:	Thu, 02 Sep 2010 08:53:12 +0200
From:	Stefani Seibold <stefani@...bold.net>
To:	dedekind1@...il.com
Cc:	David Woodhouse <dwmw2@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
	"Enzinger, Robert (EXT-Other - DE/Munich)" 
	<robert.enzinger.ext@....com>
Subject: Re: [PATCH] Add quick erase format option

Am Mittwoch, den 01.09.2010, 03:47 +0300 schrieb Artem Bityutskiy:
> Stefani,
> 
> you have strong points, but I'm still not entirely convinced.
> 
> On Tue, 2010-08-31 at 08:42 +0200, Stefani Seibold wrote:
> > > I would like to change the option name so that it would reflect the
> > > exact use-case we are creating it for: wiped out flash. So I'd be
> > > happier with something like --pristine-flash.
> > 
> > "Pristine" is not a word which non native speaker have in its
> > vocabulary.
> 
> Agree, not very simple word, when I met it in JFFS2 sources, I looked it
> up in the dictionary :-)
> 

> Also, your use-case is new/virgin/pristine/whatever NOR chips, which are
> guaranteed to be erased, and I wanted to use option name which reflects
> your use-case.
> 
> How about:
> 
> --virgin
> --factory
> --brand-new
> --all-erased
> 
> Or  :-)

--do-not-use-me is the best. But more seriously i think we should it
split it into two options. --all-erased and --check-erased. The first
assumes that all PEB are erased, while the second do the check if the
PEB is erased and if not it will be erased.

So we can handle NAND's, which have a fast erase, and NOR's  which are
very slow. With this we are able to pick the best option for the
manufacturing.

- Stefani


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ