From: Felix Fietkau <nbd@nbd.name>
To: Ryder Lee <ryder.lee@mediatek.com>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: Roy Luo <royluo@google.com>, YF Luo <yf.luo@mediatek.com>,
Yiwei Chung <yiwei.chung@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Chih-Min Chen <chih-min.Chen@mediatek.com>,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] mt76: mt7615: fix slow performance when enable encryption
Date: Fri, 7 Jun 2019 19:02:02 +0200 [thread overview]
Message-ID: <034e7eaa-5e39-57c4-1e5b-f58d41ad451a@nbd.name> (raw)
In-Reply-To: <429cf8c1421017b4030b8b6e4fa9e5cbea953d3c.1559541944.git.ryder.lee@mediatek.com>
On 2019-06-03 08:08, Ryder Lee wrote:
> Fix wrong WCID assignment and add RKV (RX Key of this entry is valid)
> flag to check if peer uses the same configuration with previous
> handshaking.
>
> If the configuration is mismatch, WTBL indicates a “cipher mismatch”
> to stop SEC decryption to prevent the packet from damage.
>
> Suggested-by: YF Luo <yf.luo@mediatek.com>
> Suggested-by: Yiwei Chung <yiwei.chung@mediatek.com>
> Signed-off-by: Ryder Lee <ryder.lee@mediatek.com>
Applied, thanks.
- Felix
next prev parent reply other threads:[~2019-06-07 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 6:08 [PATCH v3 1/2] mt76: mt7615: enable support for mesh Ryder Lee
2019-06-03 6:08 ` [PATCH v3 2/2] mt76: mt7615: fix slow performance when enable encryption Ryder Lee
2019-06-07 17:02 ` Felix Fietkau [this message]
2019-06-06 10:11 ` [PATCH v3 1/2] mt76: mt7615: enable support for mesh Sebastian Gottschall
2019-06-06 16:19 ` Lorenzo Bianconi
2019-06-07 6:03 ` Sebastian Gottschall
2019-06-09 14:36 ` Sebastian Gottschall
2019-06-10 5:11 ` possible fix for broken cmac crypto support Sebastian Gottschall
2019-06-06 10:14 ` [PATCH v3 1/2] mt76: mt7615: enable support for mesh Sebastian Gottschall
2019-06-06 15:18 ` Ryder Lee
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=034e7eaa-5e39-57c4-1e5b-f58d41ad451a@nbd.name \
--to=nbd@nbd.name \
--cc=chih-min.Chen@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=royluo@google.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=yf.luo@mediatek.com \
--cc=yiwei.chung@mediatek.com \
/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).