linux-kernel - Re: [PATCH -next] kmemcheck: build failure after merge of the slabh tree

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: <4BB0EAD0.2030807@kernel.org>
Date:	Tue, 30 Mar 2010 03:00:48 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jon Masters <jcm@...masters.org>
Subject: Re: [PATCH -next] kmemcheck: build failure after merge of the slabh
 tree

Hello,

On 03/30/2010 01:25 AM, Randy Dunlap wrote:
> This tree seems to be a bit messy.  :(

Sorry.  Most of the failures came from me forgetting to run the
conversion script on codes which are in linux-next but not mainline,
so all the new codes ended up broken by default.  I just sent out
patches against trees in linux-next.  Once they're in, there shouldn't
be many problems.

> Sorry if I missed this patch in the (email) storm.
> 
> mm/kmemcheck.c also needs slab.h added to it:

But this one is something I missed from the mainline (my script didn't
check for isolated SLAB_* flag usages).  I'll take this one into the
slabh tree.  Thanks for reporting this.  :-)

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