public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Christoph Schlameuss <schlameuss@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v5 3/4] selftests: kvm: s390: Verify reject memory region operations for ucontrol VMs
Date: Tue, 8 Oct 2024 14:56:52 +0200	[thread overview]
Message-ID: <fbed12b9-a6fb-4258-9ece-cee1b8559d92@linux.ibm.com> (raw)
In-Reply-To: <20241008074253.370481-4-schlameuss@linux.ibm.com>

On 10/8/24 9:42 AM, Christoph Schlameuss wrote:
> Add a test case verifying KVM_SET_USER_MEMORY_REGION and
> KVM_SET_USER_MEMORY_REGION2 cannot be executed on ucontrol VMs.
> 
> Executing this test case on not patched kernels will cause a null
> pointer dereference in the host kernel.
> This is fixed with commit:
> commit 7816e58967d0 ("kvm: s390: Reject memory region operations for ucontrol VMs")

I'm going to remove the "commit" prefix from the line above when picking.


  reply	other threads:[~2024-10-08 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  7:42 [PATCH v5 0/4] selftests: kvm: s390: Add ucontrol memory selftests Christoph Schlameuss
2024-10-08  7:42 ` [PATCH v5 1/4] selftests: kvm: s390: Add uc_map_unmap VM test case Christoph Schlameuss
2024-10-08  7:42 ` [PATCH v5 2/4] selftests: kvm: s390: Add uc_skey " Christoph Schlameuss
2024-10-08  7:42 ` [PATCH v5 3/4] selftests: kvm: s390: Verify reject memory region operations for ucontrol VMs Christoph Schlameuss
2024-10-08 12:56   ` Janosch Frank [this message]
2024-10-08 13:03     ` Janosch Frank
2024-10-09  8:13       ` Christoph Schlameuss
2024-10-08  7:42 ` [PATCH v5 4/4] selftests: kvm: s390: Fix whitespace confusion in ucontrol test Christoph Schlameuss
2024-10-08 12:15   ` Janosch Frank

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbed12b9-a6fb-4258-9ece-cee1b8559d92@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=schlameuss@linux.ibm.com \
    --cc=shuah@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox