| 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
| ||
|
Date: Sun, 15 Jan 2012 19:37:26 +0100 From: Pavel Machek <pavel@....cz> To: Ted Ts'o <tytso@....edu>, Vincent Pelletier <plr.vincent@...il.com>, linux-kernel@...r.kernel.org Subject: Re: ext4 bug ? "Intel 320 SSD write performance ??? contd." Hi! > > Reading this blog post[1], I thought the "2nd iteration" results could be > > considered a bug in mkfs.ext4 (and possibly any mkfs implementation): > > shouldn't mkfs run [FI]TRIM on its target before creating filesystem > > structure ? > > It's not enabled by default, because there are crappy SSD's out there > where use of the TRIM command will turn them into bricks. (No, it's > not the Intel X-25 drives that I'm worried about.) > > So I (and the distributions) don't want to make it the default, since > if you buy crap drives and then mke2fs turns them into bricks, who are > you likely to blame? The crap SSD manufacturer? Yourself for trying > to buy SSD's on the cheap? Or the program that issued the TRIM > command? Kernel for allowing userspace damage the hardware? If there are known-bad drives, we should blacklist them, and kernel should -EPERM on attempts to trim. If it is too widespread, we should probably create a whitelist... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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