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]
Date:	Thu, 14 Jun 2012 13:05:33 -0400
From:	Ted Ts'o <>
To:	Nicolas Pitre <>
Cc:	Arnd Bergmann <>,
	Alex Lemberg <>,
	Saugata Das <>,
	Artem Bityutskiy <>,
	Saugata Das <>,,,,,,
	"Luca Porzio (lporzio)" <>
Subject: Re: [PATCH 2/3] ext4: Context support

On Thu, Jun 14, 2012 at 12:14:13PM -0400, Nicolas Pitre wrote:
> Let's not forget that, in almost all cases, filesystem images are not 
> created live on the final medium.  Factories are picking a batch of 
> flash devices and a pre-built filesystem image is stamped on them, and 
> there might not even be a guarantee that those flash devices will all 
> have the same characteristics.  So to say that making this tuning at 
> mkfs time is probably not the best strategy.

Sure, that just means there needs to be a way of overriding the values
used by mke2fs.  (Because as you create the fs image, the storage
device parameters may make a difference to how blocks get allocated.)

The reason why I talk about making it work automatically at mke2fs
time is that the vast majority of created file systems (where a
specially created fs by a handset vendor counts as "one", even if it
then gets stamped on millions of devices), the end user is someone
naive/oblivious, so the right thing *has* to happen by default in the
common case of running mke2fs on the storage device where the file
system gets used.

					- Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists