linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Stanislaw Gruszka <stf_xl@wp.pl>, linux-wireless@vger.kernel.org
Cc: Herton Ronaldo Krzesinski <herton@canonical.com>,
	Hin-Tak Leung <htl10@users.sourceforge.net>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] rtl8187: fix regression on MIPS without coherent DMA
Date: Mon, 10 Feb 2014 16:50:46 -0600	[thread overview]
Message-ID: <52F957C6.40407@lwfinger.net> (raw)
In-Reply-To: <20140210213828.GA15903@localhost.localdomain>

On 02/10/2014 03:38 PM, Stanislaw Gruszka wrote:
> This patch fixes regression caused by commit a16dad77634 "MIPS: Fix
> potencial corruption". That commit fixes one corruption scenario in
> cost of adding another one, which actually start to cause crashes
> on Yeeloong laptop when rtl8187 driver is used.
>
> For correct DMA read operation on machines without DMA coherence, kernel
> have to invalidate cache, such it will refill later with new data that
> device wrote to memory, when that data is needed to process. We can only
> invalidate full cache line. Hence when cache line includes both dma
> buffer and some other data (written in cache, but not yet in main
> memory), the other data can not hit memory due to invalidation. That
> happen on rtl8187 where struct rtl8187_priv fields are located just
> before and after small buffers that are passed to USB layer and DMA
> is performed on them.
>
> To fix the problem we align buffers and reserve space after them to make
> them match cache line.
>
> This patch does not resolve all possible MIPS problems entirely, for
> that we have to assure that we always map cache aligned buffers for DMA,
> what can be complex or even not possible. But patch fixes visible and
> reproducible regression and seems other possible corruptions do not
> happen in practice, since Yeeloong laptop works stable without rtl8187
> driver.
>
> Bug report:
> https://bugzilla.kernel.org/show_bug.cgi?id=54391
>
> Reported-by: Petr Pisar <petr.pisar@atlas.cz>
> Bisected-by: Tom Li <biergaizi2009@gmail.com>
> Reported-and-tested-by: Tom Li <biergaizi2009@gmail.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
> ---

Congratulations to all for sorting this out. It could not have been too easy.

The only effect I see on architectures with DMA coherence is that the private 
data area has grown a little. Certainly, my RTL8187B device still works on x86_64.

Acked-by: Larry Finger <Larry.Finger@lwfinger.next>

Larry

>   drivers/net/wireless/rtl818x/rtl8187/rtl8187.h |   10 ++++++++--
>   1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h b/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
> index 56aee06..a6ad79f 100644
> --- a/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
> +++ b/drivers/net/wireless/rtl818x/rtl8187/rtl8187.h
> @@ -15,6 +15,8 @@
>   #ifndef RTL8187_H
>   #define RTL8187_H
>
> +#include <linux/cache.h>
> +
>   #include "rtl818x.h"
>   #include "leds.h"
>
> @@ -139,7 +141,10 @@ struct rtl8187_priv {
>   	u8 aifsn[4];
>   	u8 rfkill_mask;
>   	struct {
> -		__le64 buf;
> +		union {
> +			__le64 buf;
> +			u8 dummy1[L1_CACHE_BYTES];
> +		} ____cacheline_aligned;
>   		struct sk_buff_head queue;
>   	} b_tx_status; /* This queue is used by both -b and non-b devices */
>   	struct mutex io_mutex;
> @@ -147,7 +152,8 @@ struct rtl8187_priv {
>   		u8 bits8;
>   		__le16 bits16;
>   		__le32 bits32;
> -	} *io_dmabuf;
> +		u8 dummy2[L1_CACHE_BYTES];
> +	} *io_dmabuf ____cacheline_aligned;
>   	bool rfkill_off;
>   	u16 seqno;
>   };
>


  reply	other threads:[~2014-02-10 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 21:38 [PATCH] rtl8187: fix regression on MIPS without coherent DMA Stanislaw Gruszka
2014-02-10 22:50 ` Larry Finger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-10 23:13 Hin-Tak Leung
2014-02-11  3:09 Hin-Tak Leung

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=52F957C6.40407@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=herton@canonical.com \
    --cc=htl10@users.sourceforge.net \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stf_xl@wp.pl \
    /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).