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: Mon, 29 Jun 2009 11:38:00 +0100 From: Catalin Marinas <catalin.marinas@....com> To: Pekka Enberg <penberg@...helsinki.fi> Cc: Sergey Senozhatsky <sergey.senozhatsky@...l.by>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: kmemleak hexdump proposal On Mon, 2009-06-29 at 13:19 +0300, Pekka Enberg wrote: > On Mon, 2009-06-29 at 13:19 +0300, Sergey Senozhatsky wrote: > > Well, it's not easy to come up with something strong. > > I agree, that stack gives you almost all you need. > > > > HEX dump can give you a _tip_ in case you're not sure. > > Don't get me wrong, I'm not against it in any way. If Catalin is > interested in merging this kind of functionality, go for it! You might > want to consider unconditionally enabling the hexdump. If the > information is valuable, we should print it all the time. Though I prefer to do as much as possible in user space, I think this feature would be useful. Anyway, I may not include it before the next merging window (when is actually the best time for new features). Currently, my main focus is on reducing the false positives. -- 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