| 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
| ||
|
Date: Tue, 24 Mar 2009 10:57:54 +0200 From: Pekka Enberg <penberg@...helsinki.fi> To: Ingo Molnar <mingo@...e.hu> Cc: eduard.munteanu@...ux360.ro, linux-kernel@...r.kernel.org Subject: Re: [PATCH] kmemtrace: fix build breakage in befs On Tue, 2009-03-24 at 09:56 +0100, Ingo Molnar wrote: > * 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 :) That's what I am testing right now. It's just that I am working on an old laptop where building the kernel takes a looong time.... :-) -- 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/
Powered by blists - more mailing lists