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: Thu, 4 Dec 2014 15:56:22 +0900 From: Joonsoo Kim <iamjoonsoo.kim@....com> To: Chintan Pandya <cpandya@...eaurora.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Mel Gorman <mgorman@...e.de>, Johannes Weiner <hannes@...xchg.org>, Minchan Kim <minchan@...nel.org>, Dave Hansen <dave@...1.net>, Michal Nazarewicz <mina86@...a86.com>, Jungsoo Son <jungsoo.son@....com>, Ingo Molnar <mingo@...hat.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 6/8] mm/page_owner: keep track of page owners On Wed, Dec 03, 2014 at 06:54:08PM +0530, Chintan Pandya wrote: > Hi Kim, Hello, Chintan. > > This is really useful stuff that you are doing. And the runtime > allocation for storing page owner stack is a good call. > > Along with that, we also use extended version of the original > page_owner patch. The extension is, to store stack trace at the time > of freeing the page. That will indeed eat up space like anything > (just double of original page_owner) but it helps in debugging some > crucial issues. Like, illegitimate free, finding leaked pages (if we Sound really interesting. I hope to see it. > store their time stamps) etc. The same has been useful in finding > double-free cases in drivers. But we have never got a chance to > upstream that. Now that these patches are being discussed again, do > you think it would be good idea to integrate in the same league of > patches ? Good to hear. I think that you can upstream it separately. If you send the patch, I will review it and help to merge it. Thanks. -- 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