linux-kernel - Re: linux-next: 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]

Date:	Tue, 30 Mar 2010 14:32:59 -0500
From:	Jason Wessel <jason.wessel@...driver.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Tejun Heo <tj@...nel.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Martin Hicks <mort@....com>
Subject: Re: linux-next: build failure after merge of the slabh tree

On 03/29/2010 12:02 AM, Stephen Rothwell wrote:
> Hi Tejun,
>
> After merging the slabh tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> kernel/debug/kdb/kdb_support.c: In function 'kdb_strdup':
> kernel/debug/kdb/kdb_support.c:309: error: implicit declaration of function 'kmalloc'
> kernel/debug/kdb/kdb_support.c:309: warning: initialization makes pointer from integer without a cast
> kernel/debug/kdb/kdb_support.c: In function 'debug_kfree':
> kernel/debug/kdb/kdb_support.c:810: error: implicit declaration of function 'kfree'
>
> Caused by commit d103d3b3e8512312b5254950035366d4422a479a ("percpu: don't
> implicitly include slab.h from percpu.h") from the slabh tree interacting
> with commit 5572dd736e5577dfefafe2ad3b54760e8323e33d ("kdb: core for kgdb
> back end (1 of 2)") from the kgdb tree.
>
> I applied the following merge fixup patch which should be applied to the
> kdbg tree (see Documentation/SubmitChecklist Rule #1 :-)).
>
>   

But of course.

This is applied and will appear in kgdb-next in the next hour.

Thanks,
Jason.
--
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/