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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 11 Oct 2020 12:37:29 +0200
From:   Andrey Konovalov <>
To:     Johannes Berg <>
Cc:     Aleksandr Nogikh <>,
        "David S. Miller" <>,,
        Andrew Morton <>,
        Eric Dumazet <>,
        Dmitry Vyukov <>,
        Marco Elver <>,
        LKML <>,
        netdev <>,,
        Aleksandr Nogikh <>
Subject: Re: [PATCH v2 0/3] [PATCH v2 0/3] [PATCH v2 0/3] net, mac80211,
 kernel: enable KCOV remote coverage collection for 802.11 frame handling

On Fri, Oct 9, 2020 at 7:13 PM Johannes Berg <> wrote:
> On 9 October 2020 19:01:59 CEST, Aleksandr Nogikh <> wrote:
> >This patch series conflicts with another proposed patch
> >
> >One of these patches needs to be rebased once the other one is merged.
> Maybe that other patch shouldn't do things that way though, and add new API (which the existing one could call with some kind of "all contexts" argument) instead, so it's only necessary to specify the context (mask?) where its actually needed (the few places in usb or e whatever)?
> Surely that would also look less tedious in the mac80211 code, for example.
> And if you ever fix the nesting issue you'd have fewer places to modify again.

Hi Johannes,

I initially hesitated to do that, as it would multiply the number of
kcov callbacks. But perhaps you're right and a clean API look
outweighs the rest. I will do this in v3.


Powered by blists - more mailing lists