On Mon, Jun 18, 2007 at 09:23:55PM +0200, Thomas Bächler wrote: > Great, could you as well test if you get this problem when running > multiple luksOpen/luksClose in a short period of time, like in my first > posting in the other thread? > > It seems to me that you indeed have the same problem. Sadly, it appears > that there is no interest from the dm-crypt/cryptsetup developers to fix > this, or that none of them even reads this list. I don't think they have no interest. They might have other priorities, ie working on something that is known to be very serious - and they obviously don't see this behaviour themselves (or it should have been fixed already). I am sorry to let you down too; I am very busy with something else and I really can't have it to start debugging dmcrypt as well on top of that now. -- Carlo Wood <carlo@xxxxxxxxxx> --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
