From: Johannes Berg <johannes@sipsolutions.net>
To: Youghandhar Chintala <youghand@codeaurora.org>
Cc: Abhishek Kumar <kuabhs@chromium.org>,
Felix Fietkau <nbd@nbd.name>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Rakesh Pillai <pillair@codeaurora.org>,
Manikanta Pubbisetty <mpubbise@codeaurora.org>
Subject: Re: [PATCH 2/3] mac80211: Add support to trigger sta disconnect on hardware restart
Date: Fri, 24 Sep 2021 11:20:50 +0200 [thread overview]
Message-ID: <90d3c3c8cedcf5f8baa77b3b6e94b18656fcd0be.camel@sipsolutions.net> (raw)
In-Reply-To: <30fa98673ad816ec849f34853c9e1257@codeaurora.org>
Hi,
> We thought sending the delba would solve the problem as earlier thought
> but the actual problem is with TX PN in a secure mode.
> It is not because of delba that the Seq number and TX PN are reset to
> zero.
> It’s because of the HW restart, these parameters are reset to zero.
> Since FW/HW is the one which decides the TX PN, when it goes through
> SSR, all these parameters are reset.
Right, we solved this problem too - in a sense the driver reads the
database (not just TX PN btw, also RX replay counters) when the firmware
crashes, and sending it back after the restart. mac80211 has some hooks
for that.
johannes
next prev parent reply other threads:[~2021-09-24 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 17:23 Youghandhar Chintala
2020-12-15 17:40 ` Felix Fietkau
2021-01-28 8:08 ` youghand
2021-02-05 21:51 ` Abhishek Kumar
2021-02-12 8:37 ` Johannes Berg
2021-09-24 7:37 ` Youghandhar Chintala
2021-09-24 7:39 ` Johannes Berg
2021-09-24 9:13 ` Youghandhar Chintala
2021-09-24 9:20 ` Johannes Berg [this message]
2021-10-05 20:20 ` Jouni Malinen
2021-02-08 15:43 ` Guenter Roeck
2021-02-12 8:42 ` Johannes Berg
2021-02-12 8:44 ` Johannes Berg
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=90d3c3c8cedcf5f8baa77b3b6e94b18656fcd0be.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=kuabhs@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@codeaurora.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pillair@codeaurora.org \
--cc=youghand@codeaurora.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
Powered by JetHome