ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath10k: double check bmi xfer pointers
Date: Thu, 10 Apr 2014 06:42:43 -0700	[thread overview]
Message-ID: <53469FD3.8040001@candelatech.com> (raw)
In-Reply-To: <1397124355-6321-1-git-send-email-michal.kazior@tieto.com>

On 04/10/2014 03:05 AM, Michal Kazior wrote:
> If for some reason copy engine ring buffer became
> corrupt ath10k could crash the machine due to
> invalid pointer dereference. It's very unlikely
> but devices can never be fully trusted so verify
> if the bmi xfer pointer read back from copy engine
> matches the original pointer. The bug looked as
> follows:

Thanks for fixing this.  I'll add this patch to my
tree and run more tests today.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-04-10 13:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  4:14 Crash during driver startup Ben Greear
2014-04-10 10:05 ` [PATCH] ath10k: double check bmi xfer pointers Michal Kazior
2014-04-10 13:42   ` Ben Greear [this message]
2014-04-11  5:40   ` Kalle Valo
2014-04-11  5:47     ` Michal Kazior
2014-04-11  7:58       ` Michal Kazior
2014-04-11 15:09         ` load module ath10k: ieee80211 phy0: Failed to initialize wep: -2 Vu Hai NGUYEN
2014-04-14  6:39           ` Michal Kazior
2014-04-14  8:10             ` Kalle Valo
2014-04-14 15:49               ` RE : " Vu Hai NGUYEN
2014-04-15  8:20                 ` Report Firmware firmware-2.bin_10.1.467.2-1 Error Vu Hai NGUYEN
2014-04-15 11:02                   ` Kalle Valo
2014-04-16 11:51                     ` RE : " Vu Hai NGUYEN
2014-04-16 11:51                       ` Vu Hai NGUYEN
2014-04-24  6:35                       ` Kalle Valo
2014-04-24  9:03                         ` RE : " Vu Hai NGUYEN
2014-04-24  9:41                           ` Michal Kazior
2014-04-24 10:18                             ` Yeoh Chun-Yeow
2014-04-30 12:39                             ` RE : " Vu Hai NGUYEN
2014-05-07  7:36                               ` ath10k does not support selection antenna yet? Vu Hai NGUYEN
2014-05-07  7:48                                 ` Michal Kazior
2014-05-07  8:16                                   ` Yeoh Chun-Yeow
2014-05-07  8:16                                   ` RE : " Vu Hai NGUYEN
2014-05-07  9:26                                     ` Janusz Dziedzic
2014-05-07 14:11                                       ` Ben Greear
2014-05-07 14:21                                         ` Adrian Chadd
2014-05-07 14:33                                           ` Ben Greear
2014-05-07 14:50                                             ` Adrian Chadd
2014-05-07 15:09                                 ` Ben Greear
2014-04-14  8:05         ` [PATCH] ath10k: double check bmi xfer pointers Kalle Valo

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=53469FD3.8040001@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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