linux-kernel - Re: [PATCH 5.10 1/2] iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 4 May 2021 17:35:33 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Jari Ruusu <jariruusu@...tonmail.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        Jiri Kosina <jkosina@...e.cz>,
        Kalle Valo <kvalo@...eaurora.org>
Subject: Re: [PATCH 5.10 1/2] iwlwifi: Fix softirq/hardirq disabling in
 iwl_pcie_gen2_enqueue_hcmd()

On Tue, May 04, 2021 at 02:22:51PM +0000, Jari Ruusu wrote:
> On Tuesday, May 4, 2021 4:36 PM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > On Tue, May 04, 2021 at 01:05:56PM +0000, Jari Ruusu wrote:
> > > second patch is upstream commit e7020bb068d8be50a92f48e36b236a1a1ef9282e.
> >
> > This is not in any newer stable trees, and it was not obvious what you
> > were doing here at all.
> 
> That patch is in 5.10 + 5.11 + 5.12
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=2a442f11407ec9c9bc9b84d7155484f2b60d01f9
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.11.y&id=a9315228c1d4b1ced803761e81ef761d97f3e2fa
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.12.y&id=f935c64a0c87d86730efd6e1e168555460234d04

{sigh}

It's been a long week, I forgot to update my database of what commit is
in what stable release, my fault.

Can you resend your backports here now, and properly let us know what
kernel they belong into (again, the subject line is very confusing.)

thanks,

greg k-h