linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net, angrypenguinpoland@gmail.com,
	Qiujun Huang <hqjagain@gmail.com>,
	ath9k-devel <ath9k-devel@qca.qualcomm.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k broken [was: Linux 5.7.3]
Date: Fri, 26 Jun 2020 15:39:59 +0200	[thread overview]
Message-ID: <20200626133959.GA4024297@kroah.com> (raw)
In-Reply-To: <CAEJqkghJWGsLCj2Wvt-yhzMewjXwrXhSEDpar6rbDpbSA6R8kQ@mail.gmail.com>

On Fri, Jun 26, 2020 at 01:48:59PM +0200, Gabriel C wrote:
> Am Do., 25. Juni 2020 um 12:52 Uhr schrieb Gabriel C
> <nix.or.die@googlemail.com>:
> >
> > Am Do., 25. Juni 2020 um 12:48 Uhr schrieb Gabriel C
> > <nix.or.die@googlemail.com>:
> > >
> > > Am Do., 25. Juni 2020 um 06:57 Uhr schrieb Jiri Slaby <jirislaby@kernel.org>:
> > > >
> > > > On 25. 06. 20, 0:05, Gabriel C wrote:
> > > > > Am Mi., 17. Juni 2020 um 18:13 Uhr schrieb Greg Kroah-Hartman
> > > > > <gregkh@linuxfoundation.org>:
> > > > >>
> > > > >> I'm announcing the release of the 5.7.3 kernel.
> > > > >>
> > > > >
> > > > > Hello Greg,
> > > > >
> > > > >> Qiujun Huang (5):
> > > > >>       ath9k: Fix use-after-free Read in htc_connect_service
> > > > >>       ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
> > > > >>       ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
> > > > >>       ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
> > > > >>       ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
> > > > >>
> > > > >
> > > > > We got a report on IRC about 5.7.3+ breaking a USB ath9k Wifi Dongle,
> > > > > while working fine on <5.7.3.
> > > > >
> > > > > I don't have myself such HW, and the reported doesn't have any experience
> > > > > in bisecting the kernel, so we build kernels, each with one of the
> > > > > above commits reverted,
> > > > > to find the bad commit.
> > > > >
> > > > > The winner is:
> > > > >
> > > > > commit 6602f080cb28745259e2fab1a4cf55eeb5894f93
> > > > > Author: Qiujun Huang <hqjagain@gmail.com>
> > > > > Date:   Sat Apr 4 12:18:38 2020 +0800
> > > > >
> > > > >     ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
> > > > >
> > > > >     commit 2bbcaaee1fcbd83272e29f31e2bb7e70d8c49e05 upstream.
> > > > > ...
> > > > >
> > > > > Reverting this one fixed his problem.
> > > >
> > > > Obvious question: is 5.8-rc1 (containing the commit) broken too?
> > >
> > > Yes, it does, just checked.
> > >
> > > git tag --contains 2bbcaaee1fcbd83272e29f31e2bb7e70d8c49e05
> > > v5.8-rc1
> > > v5.8-rc2
> > >
> >
> > Sorry, I read the wrong, I just woke up.
> >
> > We didn't test 5.8-rc{1,2} yet but we will today and let you know.
> >
> 
> We tested 5.8-rc2 and it is broken too.
> 
> The exact HW name is:
> 
> TP-link tl-wn722n (Atheros AR9271 chip)

Great!

Can you work with the developers to fix this in Linus's tree first?

I bet they want to see the output of 'lsusb -v' for this device to see
if the endpoint calculations are correct...

thanks,

greg k-h

  reply	other threads:[~2020-06-26 13:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17 16:12 Linux 5.7.3 Greg Kroah-Hartman
2020-06-17 16:12 ` Greg Kroah-Hartman
2020-06-24 22:05 ` Gabriel C
2020-06-25  4:57   ` ath9k broken [was: Linux 5.7.3] Jiri Slaby
2020-06-25 10:48     ` Gabriel C
2020-06-25 10:52       ` Gabriel C
2020-06-26 11:48         ` Gabriel C
2020-06-26 13:39           ` Greg Kroah-Hartman [this message]
2020-06-26 13:51             ` Gabriel C
2020-06-26 14:40               ` Gabriel C
2020-07-07 14:11                 ` Greg Kroah-Hartman
2020-07-07 20:20                   ` Viktor Jägersküpper
2020-07-15 15:13                     ` Kalle Valo
2020-07-16  8:15                       ` Viktor Jägersküpper
2020-07-16  9:02                         ` Kalle Valo
2020-06-27 10:13     ` Roman Mamedov

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=20200626133959.GA4024297@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=angrypenguinpoland@gmail.com \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=hqjagain@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=nix.or.die@googlemail.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).