[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4b0ebaab-e287-9a2a-1696-5759f17cafef@redhat.com>
Date: Thu, 29 Aug 2019 13:56:15 +0200
From: Thomas Huth <thuth@...hat.com>
To: Janosch Frank <frankja@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ibm.com>,
kvm@...r.kernel.org
Cc: David Hildenbrand <david@...hat.com>,
Cornelia Huck <cohuck@...hat.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: s390: Test for bad access register at the start of
S390_MEM_OP
On 29/08/2019 13.15, Janosch Frank wrote:
[...]
> By the way, I think we want to check mop->size for 0 before giving it to
> vmalloc and working with it.
You're right! This currently triggers a kernel warning message with a
Call Trace! I'll add a check to my new memop selftest and send a patch...
Thomas
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists