From: Sean Christopherson <seanjc@google.com>
To: Mathias Krause <minipli@grsecurity.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: x86 - misc fixes
Date: Mon, 5 Feb 2024 11:56:39 -0800 [thread overview]
Message-ID: <ZcE9dyQ3SOuUZ8Kv@google.com> (raw)
In-Reply-To: <20240203124522.592778-1-minipli@grsecurity.net>
On Sat, Feb 03, 2024, Mathias Krause wrote:
> This is v2 of an old patch which gained an info leak fix to make it a
> series.
>
> v1 -> v2:
> - drop the stable cc, shorten commit log
> - split out dr6 change
> - add KVM_GET_MSRS stack info leak fix
In the future, please post unrelated patches separately. Bundling things into a
"misc fixes" series might seem like it's less work for maintainers, but for me at
least, it ends up being more work, e.g. to route patches into different branches.
It often ends up being more work for the contributor too, e.g. if only one patch
needs a new version.
next prev parent reply other threads:[~2024-02-05 19:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 12:45 [PATCH 0/3] KVM: x86 - misc fixes Mathias Krause
2024-02-03 12:45 ` [PATCH 1/3] KVM: x86: Fix KVM_GET_MSRS stack info leak Mathias Krause
2024-02-04 1:28 ` Xiaoyao Li
2024-02-05 18:42 ` Sean Christopherson
2024-02-06 17:52 ` Mathias Krause
2024-02-03 12:45 ` [PATCH 2/3] KVM: x86: Simplify kvm_vcpu_ioctl_x86_get_debugregs() Mathias Krause
2024-02-04 1:05 ` Xiaoyao Li
2024-02-05 19:53 ` Sean Christopherson
2024-02-06 18:15 ` Mathias Krause
2024-02-06 18:24 ` Sean Christopherson
2024-02-06 18:30 ` Mathias Krause
2024-02-06 18:32 ` Mathias Krause
2024-02-03 12:45 ` [PATCH 3/3] KVM: x86: Fix broken debugregs ABI for 32 bit kernels Mathias Krause
2024-02-05 18:46 ` Sean Christopherson
2024-02-06 18:23 ` Mathias Krause
2024-02-05 19:56 ` Sean Christopherson [this message]
2024-02-06 18:24 ` [PATCH 0/3] KVM: x86 - misc fixes Mathias Krause
2024-02-06 18:52 ` Sean Christopherson
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=ZcE9dyQ3SOuUZ8Kv@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=minipli@grsecurity.net \
--cc=pbonzini@redhat.com \
/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