| 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
| ||
|
Message-Id: <20090108144538.e5195575.akpm@linux-foundation.org> Date: Thu, 8 Jan 2009 14:45:38 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Catalin Marinas <catalin.marinas@....com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/14] Kernel memory leak detector On Fri, 19 Dec 2008 18:12:56 +0000 Catalin Marinas <catalin.marinas@....com> wrote: > A new kmemleak version is available. Sorry, I'll drop this. The level of code churn in linux-next (during the merge window!) means that I've basically lost confidence that my lameass fixed-up code will still even work. What makes things worse here is that people tromp on other people's code, or make changes without looking in linux-next to see what changes other people have made. This causes Stephen to give up and drop the offending tree, so others who had code based on that offending tree end up having a mess to deal with as well. Then, 24 or 48 hours later that tree comes back again so the mess comes back again. Please find out from Rusty (I think it's that tree?) when he's finished futzing with everything (module.c, percpu code, etc) and then respin these patches? > git://linux-arm.org/linux-2.6.git kmemleak It might be better to add that to linux-next. If we want to merge kmemleak. -- 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