Re: 2.6.24-rc2-mm1: kcryptd vs lockdep

[Ingo Molnar]

* Torsten Kaiser <just.for.lkml@xxxxxxxxxxxxxx> wrote:

> Trying the last NFSv4 patch (but that patch is only the cause, why I
> had lockdep enabled) I got this:
> [   64.550203]
> [   64.550205] =========================
> [   64.552213] [ BUG: held lock freed! ]
> [   64.553633] -------------------------
> [   64.555055] kcryptd/1022 is freeing memory
> FFFF81011EBEFB00-FFFF81011EBEFB3F, with a lock still held there!

so kcryptd frees a live, still in use bio? That could be a receipe for 
data corruption. Does SLUB_DEBUG (or SLAB_DEBUG) catch anything?

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/