From: Kalle Valo <kvalo@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, Zhi Chen <zhichen@codeaurora.org>,
ath10k@lists.infradead.org
Subject: Re: [for -stable] commit "c82919888064 ath10k: fix scan crash due to incorrect length calculation"
Date: Tue, 11 Sep 2018 17:47:31 +0300 [thread overview]
Message-ID: <87lg88t7jw.fsf@codeaurora.org> (raw)
In-Reply-To: <20180906213620.GA72542@ban.mtv.corp.google.com> (Brian Norris's message of "Thu, 6 Sep 2018 14:36:22 -0700")
Brian Norris <briannorris@chromium.org> writes:
> Hi Greg / stable maintainer(s),
>
> IIUC, this commit is a good candidate for -stable. I just hit the bug on
> 4.14, because of new vendor firmware that noticed the mismatched length
> (an internal "assert"), but it seems like this is equally problematic
> from the kernel side for as long as this code existed [1]:
>
> commit c8291988806407e02a01b4b15b4504eafbcc04e0
> Author: Zhi Chen <zhichen@codeaurora.org>
> Date: Mon Jun 18 17:00:39 2018 +0300
>
> ath10k: fix scan crash due to incorrect length calculation
>
> Thanks,
> Brian
>
> [1] I guess that would be:
>
> Fixes: ca996ec56608 ("ath10k: implement wmi-tlv backend")
>
> which was in v4.0.
FWIW:
Acked-by: Kalle Valo <kvalo@codeaurora.org>
Thanks Brian!
--
Kalle Valo
next prev parent reply other threads:[~2018-09-11 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 21:36 [for -stable] commit "c82919888064 ath10k: fix scan crash due to incorrect length calculation" Brian Norris
2018-09-11 14:47 ` Kalle Valo [this message]
2018-10-11 14:14 ` Greg KH
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=87lg88t7jw.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhichen@codeaurora.org \
/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;
as well as URLs for NNTP newsgroup(s).