[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNP3Jadj3r27Y+GhxUD_cboqn_d2BYKiqM4BzktezgjRYw@mail.gmail.com>
Date: Thu, 29 Oct 2020 19:00:07 +0100
From: Marco Elver <elver@...gle.com>
To: Dmitry Vyukov <dvyukov@...gle.com>,
Johannes Berg <johannes@...solutions.net>,
Andrey Konovalov <andreyknvl@...gle.com>
Cc: Aleksandr Nogikh <aleksandrnogikh@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>, linux-wireless@...r.kernel.org,
willemdebruijn.kernel@...il.com,
Aleksandr Nogikh <nogikh@...gle.com>
Subject: Re: [PATCH v5 3/3] mac80211: add KCOV remote annotations to incoming
frame processing
On Thu, 29 Oct 2020 at 18:44, Johannes Berg <johannes@...solutions.net> wrote:
> On Thu, 2020-10-29 at 17:36 +0000, Aleksandr Nogikh wrote:
> > From: Aleksandr Nogikh <nogikh@...gle.com>
> >
> > Add KCOV remote annotations to ieee80211_iface_work() and
> > ieee80211_rx_list(). This will enable coverage-guided fuzzing of
> > mac80211 code that processes incoming 802.11 frames.
>
> I have no idea how we'll get this merged - Jakub, do you want to take
> the whole series? Or is somebody else responsible for the core kcov
> part?
Typically core kcov changes have been going via the -mm tree.
Andrey has been making most changes to KCOV recently, so if there are
no pending changes that conflict, I don't see it's a problem for this
whole series to go through networking. I think the other series that
Andrey had been working on has been changed to only touch
drivers/usb/, so there should be no conflicts pending.
Dmitry, Andrey, is that reasonable?
> In any case,
>
> Reviewed-by: Johannes Berg <johannes@...solutions.net>
>
> johannes
>
Powered by blists - more mailing lists