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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 15 May 2012 15:22:48 +0300
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Joel Reardon <joel@...mbassador.com>
Cc:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: determining if a block erasure failed

On Tue, 2012-05-15 at 13:56 +0200, Joel Reardon wrote:
> Ah yes, if wl_wrk is freed in schedule_erase, theres no way to pass it
> back that way.
> 
> The reason is that, if erasing a block of keys fails, then those keys may
> remain on the flash device for eternity. While a rare occurance, it may be
> nice to have ubifs perform GC on all main LEBs storing the data nodes that
> can no longer be deleted through key erasure / reencrypt the valid data
> nodes.

Erasure is asynchronous and I do not see an good way to implement your
idea. Do you have a good plan?

-- 
Best Regards,
Artem Bityutskiy

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ