From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) by kanga.kvack.org (Postfix) with ESMTP id DDD056B0037 for ; Mon, 15 Sep 2014 12:24:50 -0400 (EDT) Received: by mail-pa0-f52.google.com with SMTP id kq14so6660431pab.11 for ; Mon, 15 Sep 2014 09:24:50 -0700 (PDT) Received: from bombadil.infradead.org (bombadil.infradead.org. [2001:1868:205::9]) by mx.google.com with ESMTPS id gz10si23990685pbd.137.2014.09.15.09.24.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Sep 2014 09:24:48 -0700 (PDT) Message-ID: <541712C9.5020509@infradead.org> Date: Mon, 15 Sep 2014 09:24:41 -0700 From: Randy Dunlap MIME-Version: 1.0 Subject: Re: [RFC/PATCH v2 01/10] Add kernel address sanitizer infrastructure. References: <1404905415-9046-1-git-send-email-a.ryabinin@samsung.com> <1410359487-31938-1-git-send-email-a.ryabinin@samsung.com> <1410359487-31938-2-git-send-email-a.ryabinin@samsung.com> <5414F0F3.4000001@infradead.org> <5417058E.1010206@samsung.com> In-Reply-To: <5417058E.1010206@samsung.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Andrey Ryabinin , linux-kernel@vger.kernel.org Cc: Dmitry Vyukov , Konstantin Serebryany , Dmitry Chernenkov , Andrey Konovalov , Yuri Gribov , Konstantin Khlebnikov , Sasha Levin , Christoph Lameter , Joonsoo Kim , Andrew Morton , Dave Hansen , Andi Kleen , Vegard Nossum , "H. Peter Anvin" , x86@kernel.org, linux-mm@kvack.org, Michal Marek , Ingo Molnar , Peter Zijlstra On 09/15/14 08:28, Andrey Ryabinin wrote: > On 09/14/2014 05:35 AM, Randy Dunlap wrote: >> Following sentence is confusing. I'm not sure how to fix it. >> > > > Perhaps rephrase is like this: > > Do not use slub poisoning with KASan if user tracking enabled (iow slub_debug=PU). if user tracking is enabled > User tracking info (allocation/free stacktraces) are stored inside slub object's metadata. > Slub poisoning overwrites slub object and it's metadata with poison value on freeing. its > So if KASan will detect use after free, allocation/free stacktraces will be overwritten So if KASan detects a use after free, allocation/free stacktraces are overwritten > and KASan won't be able to print them. Thanks. -- ~Randy -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org