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]
Message-ID: <YJFNyOGrF8RcTTlc@kroah.com>
Date:   Tue, 4 May 2021 15:36:08 +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 01:05:56PM +0000, Jari Ruusu wrote:
> On Tuesday, May 4, 2021 10:24 AM, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > All now queued up, thanks.
> 
> For 5.4 and 4.19 and 4.14 kernels there were 2 patches,
> first patch is upstream commit 2800aadc18a64c96b051bcb7da8a7df7d505db3f,

That one is queued up, thanks.

> 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.

> First patch modifies iwlwifi/pcie/tx.c  (older models use this)
> Second patch modifies iwlwifi/pcie/tx-gen2.c  (for newer models)
> 
> I see you queued only the "tx.c" patches, not the "tx-gen2.c" ones.

That is because it is not in 5.12.y yet either, right?

If it needs to be there, please let us know.  Having a subject line that
said "5.10" for all of these was impossible to determine...

So, for e7020bb068d8 ("iwlwifi: Fix softirq/hardirq disabling in
iwl_pcie_gen2_enqueue_hcmd()") what tree(s) do you need it in exactly?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ