linux-kernel - Re: 2.6.24-rc2-mm1: kcryptd vs lockdep

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071119075627.GB28432@elte.hu>
Date:	Mon, 19 Nov 2007 08:56:27 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Torsten Kaiser <just.for.lkml@...glemail.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.24-rc2-mm1: kcryptd vs lockdep


* Torsten Kaiser <just.for.lkml@...glemail.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/