All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: backports spatch question
Date: Mon, 5 Jul 2021 13:30:18 -0700	[thread overview]
Message-ID: <94421dca-f1b7-1f89-27d1-a981845b5a63@candelatech.com> (raw)
In-Reply-To: <40985f693651f6712aad27f1033c48d99dc5298c.camel@sipsolutions.net>

So next problem is kcov stuff.  This is just FYI, I'll just revert this
patch since I don't need it.

[greearb@ben-dt4 linux-5.13.dev.y]$ git show 261e411bb283d
commit 261e411bb283d348a6a977cccb5db393594e7695
Author: Aleksandr Nogikh <nogikh@google.com>
Date:   Thu Oct 29 17:36:20 2020 +0000

     mac80211: add KCOV remote annotations to incoming frame processing

     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.

     Signed-off-by: Aleksandr Nogikh <nogikh@google.com>
     Reviewed-by: Johannes Berg <johannes@sipsolutions.net>
     Signed-off-by: Jakub Kicinski <kuba@kernel.org>

diff --git a/net/mac80211/iface.c b/net/mac80211/iface.c
index 1be775979132..56a1bcea2c1c 100644
--- a/net/mac80211/iface.c
+++ b/net/mac80211/iface.c
@@ -1356,6 +1356,7 @@ static void ieee80211_iface_work(struct work_struct *work)
         while ((skb = skb_dequeue(&sdata->skb_queue))) {
                 struct ieee80211_mgmt *mgmt = (void *)skb->data;

+               kcov_remote_start_common(skb_get_kcov_handle(skb));
.....

Thanks,
Ben
-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  parent reply	other threads:[~2021-07-05 20:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e26b0d55-8662-ecf7-6630-ac23a99374b5@candelatech.com>
2021-07-01 21:40 ` backports spatch question Johannes Berg
2021-07-01 21:40   ` Ben Greear
2021-07-01 21:51     ` Johannes Berg
2021-07-01 22:33       ` Ben Greear
2021-07-01 22:55       ` Ben Greear
2021-07-05 17:47       ` Ben Greear
2021-07-05 17:55         ` Johannes Berg
2021-07-05 19:10           ` Ben Greear
2021-07-05 19:14             ` Johannes Berg
2021-07-05 19:17               ` Ben Greear
2021-07-05 19:19                 ` Johannes Berg
2021-07-05 19:26                   ` Ben Greear
2021-07-05 19:26                     ` Johannes Berg
2021-07-05 19:32                       ` Ben Greear
2021-07-05 19:32                         ` Johannes Berg
2021-07-05 19:38                           ` Ben Greear
2021-07-05 20:07                           ` Ben Greear
2021-07-05 20:30                           ` Ben Greear [this message]
2021-07-06  6:41                             ` Johannes Berg
2021-07-06 13:24                               ` Ben Greear

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=94421dca-f1b7-1f89-27d1-a981845b5a63@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    /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.