[PATCH] ath10k: double check bmi xfer pointers

Kalle Valo kvalo at qca.qualcomm.com
Thu Apr 10 22:40:56 PDT 2014

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?

Kalle Valo

More information about the ath10k mailing list