From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f198.google.com (mail-pf0-f198.google.com [209.85.192.198]) by kanga.kvack.org (Postfix) with ESMTP id 96D096B0261 for ; Wed, 22 Nov 2017 07:01:30 -0500 (EST) Received: by mail-pf0-f198.google.com with SMTP id x66so14429059pfe.21 for ; Wed, 22 Nov 2017 04:01:30 -0800 (PST) Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10131.outbound.protection.outlook.com. [40.107.1.131]) by mx.google.com with ESMTPS id 70si13580565ple.808.2017.11.22.04.01.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 22 Nov 2017 04:01:29 -0800 (PST) Subject: Re: [PATCH 0/5] mm/kasan: advanced check References: <20171117223043.7277-1-wen.gang.wang@oracle.com> <20171120015000.GA13507@js1304-P5Q-DELUXE> From: Andrey Ryabinin Message-ID: Date: Wed, 22 Nov 2017 15:04:51 +0300 MIME-Version: 1.0 In-Reply-To: <20171120015000.GA13507@js1304-P5Q-DELUXE> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Joonsoo Kim , Dmitry Vyukov Cc: Wengang Wang , Linux-MM , Alexander Potapenko , kasan-dev On 11/20/2017 04:50 AM, Joonsoo Kim 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? If so, I think that vchecker is more appropriate to be upstreamed. > Could you share your opinion? > Isn't everything that vchecker can do and far beyond that can be done via systemtap script using watchpoints? > Thanks. > -- 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