From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: pull-request: wireless-2023-03-10: manual merge
Date: Mon, 13 Mar 2023 09:04:33 +0100 [thread overview]
Message-ID: <be8f3f53-e1aa-1983-e8fb-9eb55c929da5@tessares.net> (raw)
In-Reply-To: <20230310114647.35422-1-johannes@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Hi Johannes,
(+cc Jakub and Stephen)
On 10/03/2023 12:46, Johannes Berg wrote:
> Hi,
>
> For now in wireless we only have a few fixes for some
> recently reported (and mostly recently introduced)
> problems.
(...)
> Johannes Berg (4):
> wifi: nl80211: fix NULL-ptr deref in offchan check
> wifi: nl80211: fix puncturing bitmap policy
FYI, we got a small conflict when merging -net in net-next in the MPTCP
tree due to this patch applied in -net:
b27f07c50a73 ("wifi: nl80211: fix puncturing bitmap policy")
and this one from net-next:
cbbaf2bb829b ("wifi: nl80211: add a command to enable/disable HW
timestamping")
The conflict has been resolved on our side[1] by keeping the
modifications from both sides and the resolution we suggest is attached
to this email.
Cheers,
Matt
[1] https://github.com/multipath-tcp/mptcp_net-next/commit/a95a213e49af
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
[-- Attachment #2: a95a213e49afeb23fc8f6ce561366886e31b5692.patch --]
[-- Type: text/x-patch, Size: 730 bytes --]
diff --cc net/wireless/nl80211.c
index 0a31b1d2845d,4f63059efd81..bfa15defc04e
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@@ -805,10 -810,8 +810,11 @@@ static const struct nla_policy nl80211_
[NL80211_ATTR_MLD_ADDR] = NLA_POLICY_EXACT_LEN(ETH_ALEN),
[NL80211_ATTR_MLO_SUPPORT] = { .type = NLA_FLAG },
[NL80211_ATTR_MAX_NUM_AKM_SUITES] = { .type = NLA_REJECT },
- [NL80211_ATTR_PUNCT_BITMAP] = NLA_POLICY_RANGE(NLA_U8, 0, 0xffff),
+ [NL80211_ATTR_PUNCT_BITMAP] =
+ NLA_POLICY_FULL_RANGE(NLA_U32, &nl80211_punct_bitmap_range),
+
+ [NL80211_ATTR_MAX_HW_TIMESTAMP_PEERS] = { .type = NLA_U16 },
+ [NL80211_ATTR_HW_TIMESTAMP_ENABLED] = { .type = NLA_FLAG },
};
/* policy for the key attributes */
next prev parent reply other threads:[~2023-03-13 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 11:46 pull-request: wireless-2023-03-10 Johannes Berg
2023-03-11 2:30 ` patchwork-bot+netdevbpf
2023-03-13 8:04 ` Matthieu Baerts [this message]
2023-03-13 9:13 ` pull-request: wireless-2023-03-10: manual merge Johannes Berg
2023-03-13 13:03 ` Matthieu Baerts
2023-03-13 17:32 ` 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=be8f3f53-e1aa-1983-e8fb-9eb55c929da5@tessares.net \
--to=matthieu.baerts@tessares.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).