From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758103AbcBDPTR (ORCPT ); Thu, 4 Feb 2016 10:19:17 -0500 Received: from mail-lf0-f45.google.com ([209.85.215.45]:35898 "EHLO mail-lf0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758042AbcBDPTP (ORCPT ); Thu, 4 Feb 2016 10:19:15 -0500 MIME-Version: 1.0 In-Reply-To: References: <1453726850-49137-1-git-send-email-dvyukov@google.com> Date: Thu, 4 Feb 2016 18:19:14 +0300 Message-ID: Subject: Re: [PATCH v6] kernel: add kcov code coverage From: Andrey Ryabinin To: Dmitry Vyukov Cc: syzkaller , Vegard Nossum , Catalin Marinas , Tavis Ormandy , Will Deacon , LKML , Quentin Casasnovas , Kostya Serebryany , Eric Dumazet , Alexander Potapenko , Kees Cook , Bjorn Helgaas , Sasha Levin , Andrew Morton , David Drysdale , linux-arm-kernel@lists.infradead.org, Ard Biesheuvel , "Kirill A. Shutemov" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2016-02-04 18:07 GMT+03:00 Dmitry Vyukov : > On Tue, Feb 2, 2016 at 5:02 PM, Andrey Ryabinin wrote: >> 2016-01-25 16:00 GMT+03:00 Dmitry Vyukov : >> >>> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug >>> index ecb9e75..cde6bd1 100644 >>> --- a/lib/Kconfig.debug >>> +++ b/lib/Kconfig.debug >>> @@ -678,6 +678,26 @@ config DEBUG_STACKOVERFLOW >>> >>> If in doubt, say "N". >>> >>> +config ARCH_HAS_KCOV >>> + bool >>> + help >>> + KCOV does not have any arch-specific code, but currently it is enabled >>> + only for x86_64. KCOV requires testing on other archs, and most likely >>> + disabling of instrumentation for some early boot code. >>> + >>> +config KCOV >>> + bool "Code coverage for fuzzing" >>> + depends on ARCH_HAS_KCOV >> >> I think we should select DEBUG_FS here, since this useless without it. > > Done in v7 > >> Also you placed this into 'Memory Debugging' submenu which seems wrong. > > Any better suggestions? > Just 'Kernel hacking' From mboxrd@z Thu Jan 1 00:00:00 1970 From: ryabinin.a.a@gmail.com (Andrey Ryabinin) Date: Thu, 4 Feb 2016 18:19:14 +0300 Subject: [PATCH v6] kernel: add kcov code coverage In-Reply-To: References: <1453726850-49137-1-git-send-email-dvyukov@google.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 2016-02-04 18:07 GMT+03:00 Dmitry Vyukov : > On Tue, Feb 2, 2016 at 5:02 PM, Andrey Ryabinin wrote: >> 2016-01-25 16:00 GMT+03:00 Dmitry Vyukov : >> >>> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug >>> index ecb9e75..cde6bd1 100644 >>> --- a/lib/Kconfig.debug >>> +++ b/lib/Kconfig.debug >>> @@ -678,6 +678,26 @@ config DEBUG_STACKOVERFLOW >>> >>> If in doubt, say "N". >>> >>> +config ARCH_HAS_KCOV >>> + bool >>> + help >>> + KCOV does not have any arch-specific code, but currently it is enabled >>> + only for x86_64. KCOV requires testing on other archs, and most likely >>> + disabling of instrumentation for some early boot code. >>> + >>> +config KCOV >>> + bool "Code coverage for fuzzing" >>> + depends on ARCH_HAS_KCOV >> >> I think we should select DEBUG_FS here, since this useless without it. > > Done in v7 > >> Also you placed this into 'Memory Debugging' submenu which seems wrong. > > Any better suggestions? > Just 'Kernel hacking'