[PATCH] ath10k: double check bmi xfer pointers

Michal Kazior michal.kazior at tieto.com
Thu Apr 10 22:47:44 PDT 2014

On 11 April 2014 07:40, Kalle Valo <kvalo at qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior at 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?

I'll look more into this.


More information about the ath10k mailing list