Re: Oopsing cryptoapi (or loop device?) on 2.6.*

[Christophe Saout <christophe@saout.de>]

Am So, den 15.02.2004 schrieb Christoph Hellwig um 19:53:

> > > What's holding it back?  I'd rather get rid of all the cryptoloop crap
> > > sooner or later.
> > 
> > Well, nothing. It's in the dm-unstable tree for some time now. It
> > depends on when Joe plans to submit it. His last words were "in the next
> > couple of months". I don't know what that means exactly.
> 
> Is there a technical reason holding it back, e.g. a depency on core DM
> changes?  If not please submit it instead of waiting any longer.

The only reason, I guess, is that it depends on this very small
dm-daemon thing:
http://people.sistina.com/~thornber/dm/patches/2.6-unstable/2.6.2/2.6.2-udm1/00016.patch

Some other dm targets in the unstable tree use this too, it's just to
have very simple bottom-half processing in a separate thread with
synchronous start and stop functions.

Especially since dm-crypt was announced in a german linux magazine two
weeks ago people keep asking me when to expect it in the kernel. And to
delay it for some months just because there might be changes to
dm-daemon, which would be almost trivial, is a stupid reason to hold it
back if you ask me. :(