linux-kernel - Re: [PATCH v2] kcov: properly check if we are in an interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 11 Oct 2016 17:06:43 +0200
From:   Andrey Konovalov <andreyknvl@...gle.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        Nicolai Stange <nicstange@...il.com>,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Kees Cook <keescook@...omium.org>,
        James Morse <james.morse@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        Vegard Nossum <vegard.nossum@...cle.com>,
        Quentin Casasnovas <quentin.casasnovas@...cle.com>,
        Andrey Ryabinin <ryabinin.a.a@...il.com>
Subject: Re: [PATCH v2] kcov: properly check if we are in an interrupt

On Tue, Oct 11, 2016 at 1:32 AM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Mon, 10 Oct 2016 19:19:11 +0200 Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
>> On Mon, Oct 10, 2016 at 6:10 PM, Andrey Konovalov <andreyknvl@...gle.com> wrote:
>> > in_interrupt() returns a nonzero value when we are either in an
>> > interrupt or have bh disabled via local_bh_disable(). Since we are
>> > interested in only ignoring coverage from actual interrupts, do a
>> > proper check instead of just calling in_interrupt().
>> >
>> > Signed-off-by: Andrey Konovalov <andreyknvl@...gle.com>
>>
>> FWIW
>> Acked-by: Dmitry Vyukov <dvyukov@...gle.com>
>>
>> This fixes a very real problem for us.
>> As per discussion in v1, other solution would involve auditing all
>> uses of in_interrupt() which needs knowledge about all drivers.
>
> OK, but I'm not seeing a description of what the problem *is*.  Could
> we please have a complete description of the user-visible effects of this
> change, for the changelog?

Mailed v3 with the description.

>