On Tue, Nov 20, 2007 at 03:40:30PM +0100, Milan Broz wrote: > (Note comment in code "It is permissible to free the struct > work_struct from inside the function that is called from it".) I don't understand yet how lockdep behaves if the work struct gets reused and the reused one finishes first.
I renamed the kcryptd functions today in an attempt to disentangle this code a bit more. - io->pending reference counting looks correct (though used inconsistently when comparing READ with WRITE) - But what happens if kcryptd_crypt_write_convert_loop() calls INIT_WORK/queue_work twice? Alasdair -- [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
