From: Greg KH <gregkh@linuxfoundation.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: stable@vger.kernel.org, linux-wireless@vger.kernel.org,
ath10k@lists.infradead.org,
Vasanthakumar Thiagarajan <vthiagar@codeaurora.org>
Subject: Re: [PATCH 2/2 - linux-stable-4.4] ath10k: rebuild crypto header in rx data frames
Date: Mon, 30 Apr 2018 12:09:01 -0700 [thread overview]
Message-ID: <20180430190901.GB8415@kroah.com> (raw)
In-Reply-To: <1525069587-19281-3-git-send-email-srirrama@codeaurora.org>
On Mon, Apr 30, 2018 at 11:56:27AM +0530, Sriram R wrote:
> Rx data frames notified through HTT_T2H_MSG_TYPE_RX_IND and
> HTT_T2H_MSG_TYPE_RX_FRAG_IND expect PN/TSC check to be done
> on host (mac80211) rather than firmware. Rebuild cipher header
> in every received data frames (that are notified through those
> HTT interfaces) from the rx_hdr_status tlv available in the
> rx descriptor of the first msdu. Skip setting RX_FLAG_IV_STRIPPED
> flag for the packets which requires mac80211 PN/TSC check support
> and set appropriate RX_FLAG for stripped crypto tail. Hw QCA988X,
> and QCA99X0 currently need the rebuilding of cipher header to
> perform PN/TSC check for replay attack.
>
> [Upstream Commit : 7eccb738fce57cbe53ed903ccf43f9ab257b15b3]
>
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@codeaurora.org>
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
> ---
> drivers/net/wireless/ath/ath10k/htt_rx.c | 98 ++++++++++++++++++++++++++------
> 1 file changed, 82 insertions(+), 16 deletions(-)
This patch breaks the build. Always test build your patches!
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-30 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 6:26 [PATCH 0/2 linux-stable-4.4] ath10k: rebuild crypto header in rx data frames Sriram R
2018-04-30 6:26 ` [PATCH 1/2 linux-stable-4.4] ath10k: Add new hw param to identify alignment for different chipsets Sriram R
2018-04-30 6:26 ` [PATCH 2/2 - linux-stable-4.4] ath10k: rebuild crypto header in rx data frames Sriram R
2018-04-30 19:09 ` Greg KH [this message]
2018-04-30 23:44 ` Sriram R
2018-05-01 0:14 ` Sriram R
2018-05-01 15:00 ` Greg KH
2018-05-01 15:18 ` Sriram R
2018-04-30 18:16 ` [PATCH 0/2 " Greg KH
2018-05-02 20:59 ` Greg KH
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=20180430190901.GB8415@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=srirrama@codeaurora.org \
--cc=stable@vger.kernel.org \
--cc=vthiagar@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;
as well as URLs for NNTP newsgroup(s).