linux-kernel - Re: [PATCH 4.4 110/268] nvme-pci: Fix nvme queue cleanup if IRQ setup fails

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 13 Jun 2018 19:13:20 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Keith Busch <keith.busch@...el.com>
Cc:     Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        Jianchao Wang <jianchao.w.wang@...cle.com>,
        stable@...r.kernel.org,
        Sasha Levin <alexander.levin@...rosoft.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4.4 110/268] nvme-pci: Fix nvme queue cleanup if IRQ
 setup fails

On Wed, Jun 13, 2018 at 10:56:32AM -0600, Keith Busch wrote:
> On Wed, Jun 13, 2018 at 05:37:35PM +0100, Ben Hutchings wrote:
> > On Wed, 2018-06-13 at 10:30 -0600, Keith Busch wrote:
> > > Thank you very much the catching that. This particular patch is indeed
> > > not correct without the following:
> > > 
> > >   161b8be2bd6ab ("nvme-pci: initialize queue memory before interrupts")
> > 
> > Oh, now I see.  Do you think that commit is suitable for stable
> > branches?
> 
> Yes, we can safely include that commit 4.4-stable. The scenario it fixes
> isn't very common in 4.4, but it could happen with quirky hardware or
> legacy interrupts.

It does not apply to 4.4.y right now, but it does apply to 4.9.y, so
I've added it there.  If it needs to get to 4.4.y, can someone do a
backport?

thanks,

greg k-h