From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzkaller <syzkaller@googlegroups.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Tavis Ormandy <taviso@google.com>,
Will Deacon <will.deacon@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Quentin Casasnovas <quentin.casasnovas@oracle.com>,
Kostya Serebryany <kcc@google.com>,
Eric Dumazet <edumazet@google.com>,
Alexander Potapenko <glider@google.com>,
Kees Cook <keescook@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Drysdale <drysdale@google.com>,
linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH v6] kernel: add kcov code coverage
Date: Thu, 4 Feb 2016 18:19:14 +0300 [thread overview]
Message-ID: <CAPAsAGx+6tfwbo32EGu6H9Mb6S1WXLvQOYzBrhhc=q=N7sFYgw@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+YygZitF6508qNX9885+nWu7iY9YVqdtE0bCA2+soTp_Q@mail.gmail.com>
2016-02-04 18:07 GMT+03:00 Dmitry Vyukov <dvyukov@google.com>:
> On Tue, Feb 2, 2016 at 5:02 PM, Andrey Ryabinin <ryabinin.a.a@gmail.com> wrote:
>> 2016-01-25 16:00 GMT+03:00 Dmitry Vyukov <dvyukov@google.com>:
>>
>>> 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'
WARNING: multiple messages have this Message-ID (diff)
From: ryabinin.a.a@gmail.com (Andrey Ryabinin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] kernel: add kcov code coverage
Date: Thu, 4 Feb 2016 18:19:14 +0300 [thread overview]
Message-ID: <CAPAsAGx+6tfwbo32EGu6H9Mb6S1WXLvQOYzBrhhc=q=N7sFYgw@mail.gmail.com> (raw)
In-Reply-To: <CACT4Y+YygZitF6508qNX9885+nWu7iY9YVqdtE0bCA2+soTp_Q@mail.gmail.com>
2016-02-04 18:07 GMT+03:00 Dmitry Vyukov <dvyukov@google.com>:
> On Tue, Feb 2, 2016 at 5:02 PM, Andrey Ryabinin <ryabinin.a.a@gmail.com> wrote:
>> 2016-01-25 16:00 GMT+03:00 Dmitry Vyukov <dvyukov@google.com>:
>>
>>> 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'
next prev parent reply other threads:[~2016-02-04 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:00 [PATCH v6] kernel: add kcov code coverage Dmitry Vyukov
2016-01-25 13:00 ` Dmitry Vyukov
2016-01-25 13:03 ` Dmitry Vyukov
2016-01-25 13:03 ` Dmitry Vyukov
2016-01-25 15:38 ` Kirill A. Shutemov
2016-01-25 15:38 ` Kirill A. Shutemov
2016-01-25 13:53 ` kbuild test robot
2016-01-25 13:53 ` kbuild test robot
2016-01-28 12:30 ` Alexander Shishkin
2016-01-28 12:30 ` Alexander Shishkin
2016-02-02 16:02 ` Andrey Ryabinin
2016-02-02 16:02 ` Andrey Ryabinin
2016-02-04 15:07 ` Dmitry Vyukov
2016-02-04 15:07 ` Dmitry Vyukov
2016-02-04 15:19 ` Andrey Ryabinin [this message]
2016-02-04 15:19 ` Andrey Ryabinin
2016-02-02 17:19 ` Jiri Slaby
2016-02-02 17:19 ` Jiri Slaby
2016-02-04 15:07 ` Dmitry Vyukov
2016-02-04 15:07 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPAsAGx+6tfwbo32EGu6H9Mb6S1WXLvQOYzBrhhc=q=N7sFYgw@mail.gmail.com' \
--to=ryabinin.a.a@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=drysdale@google.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=keescook@google.com \
--cc=kirill@shutemov.name \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.casasnovas@oracle.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=taviso@google.com \
--cc=vegard.nossum@oracle.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.