From: Pkshih <pkshih@realtek.com>
To: "baijiaju1990@gmail.com" <baijiaju1990@gmail.com>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"kuba@kernel.org" <kuba@kernel.org>,
"straube.linux@gmail.com" <straube.linux@gmail.com>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtl8192ce: avoid accessing the data mapped to streaming DMA
Date: Wed, 28 Oct 2020 04:41:24 +0000 [thread overview]
Message-ID: <1603860037.8609.4.camel@realtek.com> (raw)
In-Reply-To: <20201019030931.4796-1-baijiaju1990@gmail.com>
On Mon, 2020-10-19 at 11:09 +0800, Jia-Ju Bai wrote:
> In rtl92ce_tx_fill_cmddesc(), skb->data is mapped to streaming DMA on
> line 530:
> dma_addr_t mapping = dma_map_single(..., skb->data, ...);
>
> On line 533, skb->data is assigned to hdr after cast:
> struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)(skb->data);
>
> Then hdr->frame_control is accessed on line 534:
> __le16 fc = hdr->frame_control;
>
> This DMA access may cause data inconsistency between CPU and hardwre.
>
> To fix this bug, hdr->frame_control is accessed before the DMA mapping.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
> ---
> drivers/net/wireless/realtek/rtlwifi/rtl8192ce/trx.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/trx.c
> b/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/trx.c
> index c0635309a92d..4165175cf5c0 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/trx.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/rtl8192ce/trx.c
> @@ -527,12 +527,12 @@ void rtl92ce_tx_fill_cmddesc(struct ieee80211_hw *hw,
> u8 fw_queue = QSLT_BEACON;
> __le32 *pdesc = (__le32 *)pdesc8;
>
> - dma_addr_t mapping = dma_map_single(&rtlpci->pdev->dev, skb->data,
> - skb->len, DMA_TO_DEVICE);
> -
> struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)(skb->data);
> __le16 fc = hdr->frame_control;
>
> + dma_addr_t mapping = dma_map_single(&rtlpci->pdev->dev, skb->data,
> + skb->len, DMA_TO_DEVICE);
> +
> if (dma_mapping_error(&rtlpci->pdev->dev, mapping)) {
> rtl_dbg(rtlpriv, COMP_SEND, DBG_TRACE,
> "DMA mapping error\n");
The changes of the series patches are good to me.
But, please use 'rtlwifi: ' as subject prefix, like "rtlwifi: rtl8192ce: ...",
and send them as a patchset I think this would be better to maintainer.
Thank you
---
PK
next prev parent reply other threads:[~2020-10-29 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 3:09 [PATCH] rtl8192ce: avoid accessing the data mapped to streaming DMA Jia-Ju Bai
2020-10-28 4:41 ` Pkshih [this message]
2020-11-07 11:44 ` Kalle Valo
[not found] ` <20201107114412.4BEEAC433C9@smtp.codeaurora.org>
2020-11-18 1:56 ` Jia-Ju Bai
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=1603860037.8609.4.camel@realtek.com \
--to=pkshih@realtek.com \
--cc=Larry.Finger@lwfinger.net \
--cc=baijiaju1990@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=straube.linux@gmail.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).