linux-kernel - Re: [BUILD_FAILURE] next-20090115 - s390x

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: <1232038838.32016.73.camel@pc1117.cambridge.arm.com>
Date:	Thu, 15 Jan 2009 17:00:38 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-s390@...r.kernel.org, schwidefsky@...ibm.com,
	penberg@...helsinki.fi
Subject: Re: [BUILD_FAILURE] next-20090115 - s390x - mm/kmemleak.c

On Thu, 2009-01-15 at 13:05 +0100, Heiko Carstens wrote:
> Btw. you have
> 
> /*
>  * Stop the automatic memory scanning thread. This function must be called
>  * with the kmemleak_mutex held.
>  */
> void stop_scan_thread(void)
> {
> ...
> 
> but call the function unlocked from kmemleak_write. Looks like a bug ;)

kmemleak_write() is called with the kmemleak_mutex acquired in the
kmemleak_open() function (and released in kmemleak_release()).

-- 
Catalin

--
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/