From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: traceability of wifi packet drops
Date: Mon, 27 Mar 2023 16:31:51 +0200 [thread overview]
Message-ID: <e3ca82aaf29f92303d5dec239d2177029e91c134.camel@sipsolutions.net> (raw)
In-Reply-To: <00659771ed54353f92027702c5bbb84702da62ce.camel@sipsolutions.net>
On Mon, 2023-03-27 at 16:19 +0200, Johannes Berg wrote:
>
> SKB_DROP_REASON_MAC80211_DUP (SKB_DROP_REASON_MAC80211_TYPE_UNUSABLE | 1)
> SKB_DROP_REASON_MAC80211_BAD_BIP_KEYIDX (SKB_DROP_REASON_MAC80211_TYPE_MONITOR | 1)
>
Ah, this would lose the ability to immediately see monitor/unusable, so
we'd have to make the names even longer :(
Maybe some creative macro such as
DROP_UNUSABLE(DUP)
DROP_MONITOR(BAD_BIP_KEYIDX)
could be done, but that hurts ctags/elixir and the likes ...
johannes
next prev parent reply other threads:[~2023-03-27 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:19 traceability of wifi packet drops Johannes Berg
2023-03-27 14:31 ` Johannes Berg [this message]
2023-03-28 1:09 ` Jakub Kicinski
2023-03-28 2:27 ` Dave Taht
2023-03-28 7:37 ` Johannes Berg
2023-03-28 8:16 ` Eric Dumazet
2023-03-28 8:18 ` Johannes Berg
2023-03-28 22:58 ` Jakub Kicinski
2023-03-29 8:35 ` Johannes Berg
2023-03-29 18:02 ` Jakub Kicinski
2023-03-29 18:57 ` Johannes Berg
2023-03-29 19:09 ` Jakub Kicinski
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=e3ca82aaf29f92303d5dec239d2177029e91c134.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).