From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <greearb@candelatech.com>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: double check bmi xfer pointers
Date: Fri, 11 Apr 2014 08:40:56 +0300 [thread overview]
Message-ID: <8738hkh193.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1397124355-6321-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 10 Apr 2014 12:05:55 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> 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 big question is why does this happen? Does this happen only with
Ben's firmware or is it a more generic problem?
--
Kalle Valo
next prev parent reply other threads:[~2014-04-11 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53461A8A.4030209@candelatech.com>
2014-04-10 10:05 ` [PATCH] ath10k: double check bmi xfer pointers Michal Kazior
2014-04-10 13:42 ` Ben Greear
2014-04-11 5:40 ` Kalle Valo [this message]
2014-04-11 5:47 ` Michal Kazior
2014-04-11 7:58 ` Michal Kazior
2014-04-14 8:05 ` 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=8738hkh193.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--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