stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: "Pali Rohár" <pali@kernel.org>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, "Kalle Valo" <kvalo@codeaurora.org>,
	linux-wireless@vger.kernel.org
Subject: Re: Backporting CVE-2020-3702 ath9k patches to stable
Date: Fri, 20 Aug 2021 19:49:14 -0400	[thread overview]
Message-ID: <YSA/euLpnAqmoq5b@sashalap> (raw)
In-Reply-To: <87y28vycox.fsf@toke.dk>

On Sat, Aug 21, 2021 at 12:27:10AM +0200, Toke Høiland-Jørgensen wrote:
>Sasha Levin <sashal@kernel.org> writes:
>> On Fri, Aug 20, 2021 at 01:35:05PM +0200, Pali Rohár wrote:
>>>It is sad, but Qualcomm support said that they have fixed it in their
>>>proprietary driver in July 2020 (so more than year ago) and that open
>>>source drivers like ath9k are unsupported and customers should not use
>>>them :( And similar answer is from vendors who put these chips into
>>>their cards / products.
>>
>> Is there a public statement that says that? Right now the MAINTAINERS
>> file says it's "supported" and if it's not the case we should at least
>> fix that and consider deprecating it if it's really orphaned.
>
>FWIW there's still quite a few OpenWrt devices that are using ath9k and
>ticking away happily. And we are some that do still care about ath9k,
>even if QCA doesn't... As the email that started this thread also shows,
>I suppose?

Thats obviously true, and if there are people who care about this then
they should both get the tools needed from the community to do their
work as well as the credit for getting the work done.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2021-08-20 23:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  8:48 Backporting CVE-2020-3702 ath9k patches to stable Pali Rohár
2021-08-18  9:02 ` Greg KH
2021-08-18  9:10   ` Pali Rohár
2021-08-18  9:18     ` Greg KH
2021-08-20 11:35       ` Pali Rohár
2021-08-20 21:23         ` Sasha Levin
2021-08-20 22:27           ` Toke Høiland-Jørgensen
2021-08-20 23:07             ` Pali Rohár
2021-08-20 23:49             ` Sasha Levin [this message]
2021-08-20 22:41           ` Pali Rohár
2021-09-02 11:48       ` Pavel Machek
2021-09-02 12:02         ` Greg KH
2021-09-03  6:34           ` Pavel Machek
2021-09-06  8:49             ` Greg KH
2021-09-11  7:46               ` Pavel Machek

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=YSA/euLpnAqmoq5b@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=toke@redhat.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;
as well as URLs for NNTP newsgroup(s).