From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f200.google.com (mail-pf0-f200.google.com [209.85.192.200]) by kanga.kvack.org (Postfix) with ESMTP id 9F2B66B0268 for ; Mon, 20 Nov 2017 15:20:42 -0500 (EST) Received: by mail-pf0-f200.google.com with SMTP id s28so9700353pfg.6 for ; Mon, 20 Nov 2017 12:20:42 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id 34sor4219395plz.143.2017.11.20.12.20.41 for (Google Transport Security); Mon, 20 Nov 2017 12:20:41 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <37111d5b-7042-dfff-9ac7-8733b77930e8@oracle.com> References: <20171117223043.7277-1-wen.gang.wang@oracle.com> <20171120015000.GA13507@js1304-P5Q-DELUXE> <37111d5b-7042-dfff-9ac7-8733b77930e8@oracle.com> From: Dmitry Vyukov Date: Mon, 20 Nov 2017 21:20:20 +0100 Message-ID: Subject: Re: [PATCH 0/5] mm/kasan: advanced check Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: To: Wengang Cc: Joonsoo Kim , Linux-MM , Andrey Ryabinin , Alexander Potapenko , kasan-dev On Mon, Nov 20, 2017 at 9:05 PM, Wengang wrote: > > > On 11/20/2017 12:41 AM, Dmitry Vyukov wrote: >> >> >>> >>> The reason I didn't submit the vchecker to mainline is that I didn't find >>> the case that this tool is useful in real life. Most of the system broken >>> case >>> can be debugged by other ways. Do you see the real case that this tool is >>> helpful? >> >> Hi, >> >> Yes, this is the main question here. >> How is it going to be used in real life? How widely? >> > > I think the owner check can be enabled in the cases where KASAN is used. -- > That is that we found there is memory issue, but don't know how it happened. But KASAN generally pinpoints the corruption as it happens. Why do we need something else? -- 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