linux-kernel - Re: [PATCH] kmemtrace: fix build breakage in befs

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, 24 Mar 2009 09:56:58 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	eduard.munteanu@...ux360.ro, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kmemtrace: fix build breakage in befs


* Pekka Enberg <penberg@...helsinki.fi> wrote:

> On Tue, 2009-03-24 at 09:51 +0100, Ingo Molnar wrote:
> > there's another build problem as well, in squashfs, and in key.h:
> > 
> >  include/linux/key.h:128: error: field 'sem' has incomplete type
> >  fs/squashfs/export.c:133: error: implicit declaration of function 'kmalloc'
> >  fs/squashfs/export.c:143: error: implicit declaration of function 'kfree'
> > 
> > And i suspect there's more as well. Is there really no unintrusive 
> > way to solve this - or do you think the RCU change reduces the 
> > include file spaghetti?
> 
> I don't think there is and yes, I do think the RCU change cleans 
> up things as well.

Okay. Note, you'll have to test tip:tracing/kmemtrace explicitly as 
i had to exclude it from tip:master due to test failures. Will put 
it back in once fixes arrive :)

	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/