linux-kernel - Re: [PATCH 4.20 193/352] KVM: s390: unregister debug feature on failing arch init

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:   Mon, 11 Feb 2019 17:53:21 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Christian Borntraeger <borntraeger@...ibm.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Michael Mueller <mimu@...ux.ibm.com>,
        Cornelia Huck <cohuck@...hat.com>,
        Pierre Morel <pmorel@...ux.ibm.com>,
        David Hildenbrand <david@...hat.com>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.20 193/352] KVM: s390: unregister debug feature on
 failing arch init

On Mon, Feb 11, 2019 at 03:34:20PM +0100, Christian Borntraeger wrote:
> 
> On 11.02.2019 15:17, Greg Kroah-Hartman wrote:
> > 4.20-stable review patch.  If anyone has any objections, please let me know.
> > 
> > ------------------
> > 
> > [ Upstream commit 308c3e6673b012beecb96ef04cc65f4a0e7cdd99 ]
> > 
> > Make sure the debug feature and its allocated resources get
> > released upon unsuccessful architecture initialization.
> > 
> > A related indication of the issue will be reported as kernel
> > message.
> > 
> > Signed-off-by: Michael Mueller <mimu@...ux.ibm.com>
> > Reviewed-by: Cornelia Huck <cohuck@...hat.com>
> > Reviewed-by: Pierre Morel <pmorel@...ux.ibm.com>
> > Reviewed-by: David Hildenbrand <david@...hat.com>
> > Message-Id: <20181130143215.69496-2-mimu@...ux.ibm.com>
> > Signed-off-by: Christian Borntraeger <borntraeger@...ibm.com>
> > Signed-off-by: Sasha Levin <sashal@...nel.org>
> 
> It does not hurt, but I explicitly did not cc stable for this patch as 
> kvm_register_device_ops only fails in case of a code error.

Fair enough, I've dropped it from all trees now, thanks.

greg k-h