From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>,
ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org,
Qiujun Huang <hqjagain@gmail.com>,
Mark O'Donovan <shiftee@posteo.net>,
Roman Mamedov <rm@romanrm.net>
Subject: Re: Please apply "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb" and the corresponding fix to all stable kernels
Date: Mon, 27 Jul 2020 15:29:14 +0200 [thread overview]
Message-ID: <20200727132914.GA3982320@kroah.com> (raw)
In-Reply-To: <81f07366-59e4-bfc9-c7a6-95c8e686c5e1@freenet.de>
On Mon, Jul 27, 2020 at 01:20:11PM +0200, Viktor Jägersküpper wrote:
> Hi Greg, Sasha and all the others,
>
> Hans de Goede requested to revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
> from all stable and longterm kernels because this commit broke certain devices
> with Atheros 9271 and at that time it seemed that reverting the commit would be
> done in the mainline kernel. The revert was done in kernel 5.7.9 etc., however
> Mark O'Donovan found a fix for the original commit - which avoided the revert in
> the mainline kernel - and this fix is now included in 5.8-rc7 with commit
>
> 92f53e2fda8bb9a559ad61d57bfb397ce67ed0ab ("ath9k: Fix regression with Atheros 9271").
>
> To be consistent with the mainline kernel, please apply the original commit
> again (or re-revert it, whatever is appropriate for stable kernels) and then
> apply Mark's fix. I have tested this with the current 5.7.10 kernel to confirm
> that it works because I was affected by the bug.
>
> All relevant people are CC'ed if someone wants to object.
I've now queued both up, thanks!
greg k-h
prev parent reply other threads:[~2020-07-27 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 11:20 Please apply "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb" and the corresponding fix to all stable kernels Viktor Jägersküpper
2020-07-27 13:29 ` Greg Kroah-Hartman [this message]
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=20200727132914.GA3982320@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=hqjagain@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rm@romanrm.net \
--cc=sashal@kernel.org \
--cc=shiftee@posteo.net \
--cc=stable@vger.kernel.org \
--cc=viktor_jaegerskuepper@freenet.de \
/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).