[PATCH] ath10k: add extra check for frame tracing

Kalle Valo kvalo at qca.qualcomm.com
Thu Apr 16 23:34:32 PDT 2015

Michal Kazior <michal.kazior at tieto.com> writes:

> Frames are logged via tracing in two slices:
> header and payload, separately. This is done for
> performance reasons when one wants to, e.g.
> analyse metadata only of frames only.
> If for some reason device delivered a frame buffer
> which was sized below what 802.11 header implied
> tracing logic would blow doing an invalid memory
> accesses.
> I've hit this problem when running IBSS on QCA988X
> with 999.999.0.636 and tracing at the same time.
> Fixes: 5ce8e7fdcc7a ("ath10k: handle ieee80211 header and payload tracing separately")
> Signed-off-by: Michal Kazior <michal.kazior at tieto.com>

Thanks, applied.

Kalle Valo

More information about the ath10k mailing list