From: Miri Korenblit <miriam.rachel.korenblit@intel.com>
To: linux-wireless@vger.kernel.org
Cc: Daniel Gabay <daniel.gabay@intel.com>
Subject: [PATCH v5 wireless-next 07/12] wifi: cfg80211: allow ToDS=0/FromDS=0 data frames on NAN data interfaces
Date: Wed, 18 Mar 2026 14:39:21 +0200 [thread overview]
Message-ID: <20260318123926.206536-8-miriam.rachel.korenblit@intel.com> (raw)
In-Reply-To: <20260318123926.206536-1-miriam.rachel.korenblit@intel.com>
From: Daniel Gabay <daniel.gabay@intel.com>
According to Wi-Fi Aware (TM) specification Table 3, data frame should
have 0 in the FromDS/ToDS fields. Don't drop received frames with 0
FromDS/ToDS if they are received on NAN_DATA interface.
While at it, fix a double indent.
Signed-off-by: Daniel Gabay <daniel.gabay@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20260108102921.de5f318a790a.Id34dd69552920b579e6881ffd38fa692a491b601@changeid
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20260219094725.3846371-5-miriam.rachel.korenblit@intel.com
---
net/wireless/util.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/net/wireless/util.c b/net/wireless/util.c
index 8dda571585cf..6769ef55ee59 100644
--- a/net/wireless/util.c
+++ b/net/wireless/util.c
@@ -625,8 +625,9 @@ int ieee80211_data_to_8023_exthdr(struct sk_buff *skb, struct ethhdr *ehdr,
case cpu_to_le16(0):
if (iftype != NL80211_IFTYPE_ADHOC &&
iftype != NL80211_IFTYPE_STATION &&
- iftype != NL80211_IFTYPE_OCB)
- return -1;
+ iftype != NL80211_IFTYPE_OCB &&
+ iftype != NL80211_IFTYPE_NAN_DATA)
+ return -1;
break;
}
--
2.34.1
next prev parent reply other threads:[~2026-03-18 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 12:39 [PATCH v5 wireless-next 00/12] wifi: cfg80211/nl80211: Add NAN Data Path support Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 01/12] wifi: cfg80211: Add an API to configure local NAN schedule Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 02/12] wifi: cfg80211: make sure NAN chandefs are valid Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 03/12] wifi: cfg80211: add support for NAN data interface Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 04/12] wifi: cfg80211: separately store HT, VHT and HE capabilities for NAN Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 05/12] wifi: nl80211: add support for NAN stations Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 06/12] wifi: nl80211: define an API for configuring the NAN peer's schedule Miri Korenblit
2026-03-18 12:39 ` Miri Korenblit [this message]
2026-03-18 12:39 ` [PATCH v5 wireless-next 08/12] wifi: nl80211: allow reporting spurious NAN Data frames Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 09/12] wifi: nl80211: add NL80211_CMD_NAN_ULW_UPDATE notification Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 10/12] wifi: nl80211: Add a notification to notify NAN channel evacuation Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 11/12] wifi: ieee80211: Add some missing NAN definitions Miri Korenblit
2026-03-18 12:39 ` [PATCH v5 wireless-next 12/12] wifi: cfg80211: allow protected action frame TX for NAN Miri Korenblit
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=20260318123926.206536-8-miriam.rachel.korenblit@intel.com \
--to=miriam.rachel.korenblit@intel.com \
--cc=daniel.gabay@intel.com \
--cc=linux-wireless@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