linux-ext4 - Re: [PATCH] mke2fs: restore verbose message for BLKDISCARD

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: <20130308190635.GC12008@thunk.org>
Date:	Fri, 8 Mar 2013 14:06:35 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Lukáš Czerner <lczerner@...hat.com>,
	Chris Ball <cjb@...top.org>, linux-ext4@...r.kernel.org,
	Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] mke2fs: restore verbose message for BLKDISCARD

Here's an idea.  What if we set a timer when send the first probing
discard, and if it takes too long, we print an error message and then
try to recover.

More generally, if we can't trust a device's advertised discard
parameters, maybe it makes sense to create a userspace program that
benchmarks the device to determine various critical flash parameters,
including "does discard really work?"  "Is it hopelessly slow"', and
"what is the erase block size"?  This program can then send the
appropriate parameters to a filesystem's mkfs program.

   	      	      	  	   - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html