From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail177-1.suw61.mandrillapp.com ([198.2.177.1]:3941 "EHLO mail177-1.suw61.mandrillapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752379AbcCAIQh (ORCPT ); Tue, 1 Mar 2016 03:16:37 -0500 Received: from pmta06.mandrill.prod.suw01.rsglab.com (127.0.0.1) by mail177-1.suw61.mandrillapp.com id hql7ua22rtkv for ; Tue, 1 Mar 2016 08:16:14 +0000 (envelope-from ) From: Greg KH Subject: Re: [PATCH 2/2] KVM: s390: fix memory overwrites when vx is disabled To: David Hildenbrand Cc: , , Message-Id: <20160301075536.GA11111@kroah.com> References: <1456327495-76013-1-git-send-email-dahi@linux.vnet.ibm.com> <1456327495-76013-2-git-send-email-dahi@linux.vnet.ibm.com> <20160301050651.GA3200@kroah.com> <20160301081904.072d0807@thinkpad-w530> In-Reply-To: <20160301081904.072d0807@thinkpad-w530> Date: Tue, 01 Mar 2016 08:16:14 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On Tue, Mar 01, 2016 at 08:19:04AM +0100, David Hildenbrand wrote: > > On Wed, Feb 24, 2016 at 04:24:55PM +0100, David Hildenbrand wrote: > > > This is the backport of 9abc2a08a7d6 (KVM: s390: fix memory overwrites > > > when vx is disabled) for 4.4-stable. > > > > This backport didn't apply: > > > > Applying kvm-s390-fix-memory-overwrites-when-vx-is-disabled.patch to linux-4.4.y > > Applying patch kvm-s390-fix-memory-overwrites-when-vx-is-disabled.patch > > patching file arch/s390/include/asm/kvm_host.h > > patching file arch/s390/kvm/kvm-s390.c > > Hunk #8 FAILED at 2246. > > Hunk #9 FAILED at 2255. > > 2 out of 10 hunks FAILED -- rejects in file arch/s390/kvm/kvm-s390.c > > > > Can you try it again? > > > > thanks, > > > > greg k-h > > > > Hi Greg, > > did you take care of the mentioned precondition? > > # v4.4 d9a3a09af54d s390/kvm: remove dependency on struct save_area definition I did not, I missed that as I assumed it was the previous patch here, sorry. > But as I just received the mail saying this patch has been added to 4.4, I > assume that this problems is solved :) No, that was a mistake, I then deleted it. But, I've added it again now and the dependency so all is fine, sorry for the noise. greg k-h