Messages in this thread | | | Date | Sun, 15 Feb 2004 19:46:33 +0000 | From | Christoph Hellwig <> | Subject | Re: Oopsing cryptoapi (or loop device?) on 2.6.* |
| |
On Sun, Feb 15, 2004 at 08:36:00PM +0100, Christophe Saout wrote: > 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. :(
Well, actually the above code should not enter the kernel tree at all. Care to rewrite dm-crypt to use Rusty's kthread code in -mm instead and submit a patch to Andrew? Whenever he merges the kthread stuff to mainline he could just include dm-crypt then. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |