From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756766AbcAYPiN (ORCPT ); Mon, 25 Jan 2016 10:38:13 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:35118 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751758AbcAYPiK (ORCPT ); Mon, 25 Jan 2016 10:38:10 -0500 Date: Mon, 25 Jan 2016 17:38:07 +0200 From: "Kirill A. Shutemov" 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 , Andrey Ryabinin , Peter Zijlstra , Alexander Shishkin Subject: Re: [PATCH v6] kernel: add kcov code coverage Message-ID: <20160125153806.GA12391@node.shutemov.name> References: <1453726850-49137-1-git-send-email-dvyukov@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 25, 2016 at 02:03:55PM +0100, Dmitry Vyukov wrote: > On Mon, Jan 25, 2016 at 2:00 PM, Dmitry Vyukov wrote: > > kcov provides code coverage collection for coverage-guided fuzzing > > (randomized testing). Coverage-guided fuzzing is a testing technique > > that uses coverage feedback to determine new interesting inputs to a > > system. A notable user-space example is AFL > > (http://lcamtuf.coredump.cx/afl/). However, this technique is not > > widely used for kernel testing due to missing compiler and kernel > > support. > > Kirill, I export kcov file as 0600 now. > > Any more comments? Acked-by: Kirill A. Shutemov I have some doubts if debugfs knob is the right way to go. Maybe it would be better to integrate the feature with perf somehow as it has tracing capabilities. But that's just a side note. I don't have a strong opinion about the interface. +CC perf people. -- Kirill A. Shutemov From mboxrd@z Thu Jan 1 00:00:00 1970 From: kirill@shutemov.name (Kirill A. Shutemov) Date: Mon, 25 Jan 2016 17:38:07 +0200 Subject: [PATCH v6] kernel: add kcov code coverage In-Reply-To: References: <1453726850-49137-1-git-send-email-dvyukov@google.com> Message-ID: <20160125153806.GA12391@node.shutemov.name> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Jan 25, 2016 at 02:03:55PM +0100, Dmitry Vyukov wrote: > On Mon, Jan 25, 2016 at 2:00 PM, Dmitry Vyukov wrote: > > kcov provides code coverage collection for coverage-guided fuzzing > > (randomized testing). Coverage-guided fuzzing is a testing technique > > that uses coverage feedback to determine new interesting inputs to a > > system. A notable user-space example is AFL > > (http://lcamtuf.coredump.cx/afl/). However, this technique is not > > widely used for kernel testing due to missing compiler and kernel > > support. > > Kirill, I export kcov file as 0600 now. > > Any more comments? Acked-by: Kirill A. Shutemov I have some doubts if debugfs knob is the right way to go. Maybe it would be better to integrate the feature with perf somehow as it has tracing capabilities. But that's just a side note. I don't have a strong opinion about the interface. +CC perf people. -- Kirill A. Shutemov