From: Sean Christopherson <seanjc@google.com>
To: pbonzini@redhat.com, shuah@kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Patrick Roy <roypat@amazon.co.uk>
Cc: chao.p.peng@linux.intel.com, ackerleytng@google.com,
graf@amazon.com, jgowans@amazon.com
Subject: Re: [PATCH] kvm: selftest: fix noop test in guest_memfd_test.c
Date: Mon, 4 Nov 2024 21:53:42 -0800 [thread overview]
Message-ID: <Zymy5hjgMSMT64uI@google.com> (raw)
In-Reply-To: <173039504313.1508539.4634909288183844362.b4-ty@google.com>
On Thu, Oct 31, 2024, Sean Christopherson wrote:
> On Thu, 24 Oct 2024 10:59:53 +0100, Patrick Roy wrote:
> > The loop in test_create_guest_memfd_invalid that is supposed to test
> > that nothing is accepted as a valid flag to KVM_CREATE_GUEST_MEMFD was
> > initializing `flag` as 0 instead of BIT(0). This caused the loop to
> > immediately exit instead of iterating over BIT(0), BIT(1), ... .
>
> Applied to kvm-x86 fixes, thanks!
>
> [1/1] kvm: selftest: fix noop test in guest_memfd_test.c
> https://github.com/kvm-x86/linux/commit/fd5b88cc7fbf
FYI, I rebased "fixes" onto 6.12-rc5 to avoid several pointless conflicts in
other patches. New hash:
[1/1] KVM: selftests: fix unintentional noop test in guest_memfd_test.c
https://github.com/kvm-x86/linux/commit/945bdae20be5
prev parent reply other threads:[~2024-11-05 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 9:59 [PATCH] kvm: selftest: fix noop test in guest_memfd_test.c Patrick Roy
2024-10-24 10:19 ` Gowans, James
2024-10-26 8:59 ` Muhammad Usama Anjum
2024-10-31 19:51 ` Sean Christopherson
2024-11-05 5:53 ` Sean Christopherson [this message]
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=Zymy5hjgMSMT64uI@google.com \
--to=seanjc@google.com \
--cc=ackerleytng@google.com \
--cc=chao.p.peng@linux.intel.com \
--cc=graf@amazon.com \
--cc=jgowans@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=roypat@amazon.co.uk \
--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