| 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: <1249980905.27150.11.camel@pc1117.cambridge.arm.com> Date: Tue, 11 Aug 2009 09:55:05 +0100 From: Catalin Marinas <catalin.marinas@....com> To: Ingo Molnar <mingo@...e.hu> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: kmemleak: Protect the seq start/next/stop sequence by rcu_read_lock() On Tue, 2009-08-11 at 09:32 +0200, Ingo Molnar wrote: > * Catalin Marinas <catalin.marinas@....com> wrote: > > I tried similar config and with the mainline kernel I get some > > lockups (several seconds) with CONFIG_PREEMPT disabled on ARM > > machines or x86 during a scanning episode but it eventually > > completes the scanning. With the kmemleak patches for the next > > merging window, I don't get any lockups as it has more > > cond_resched() calls. > > How big are those patches? Kmemleak is new in .31 so if it fixes a > real problem it might still be acceptable. My patches for -next were posted here - http://lkml.org/lkml/2009/7/24/166 - but the relevant ones are pretty small (review/ack is welcomed): http://lkml.org/lkml/2009/7/24/176 - allow rescheduling during object scanning http://lkml.org/lkml/2009/7/24/173 - inform kmemleak about kernel stack allocation (needs ack by the x86 people) http://lkml.org/lkml/2009/7/24/172 - always scan the task stacks -- Catalin -- 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