From: Paolo Bonzini <pbonzini@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Thomas Garnier" <thgarnie@google.com>,
"Andy Lutomirski" <luto@amacapital.net>,
"Jim Mattson" <jmattson@google.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
"Andrey Ryabinin" <aryabinin@virtuozzo.com>,
"Alexander Potapenko" <glider@google.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Kees Cook" <keescook@chromium.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Borislav Petkov" <bp@suse.de>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <len.brown@intel.com>, "Pavel Machek" <pavel@ucw.cz>,
"Jiri Kosina" <jikos@kernel.org>,
"Matt Fleming" <matt@codeblueprint.co.uk>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Juergen Gross" <jgross@suse.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Peter Zijlstra" <peterz@infradead.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
"He Chen" <he.chen@linux.intel.com>,
"Brian Gerst" <brgerst@gmail.com>,
"Stanislaw Gruszka" <sgruszka@redhat.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Adam Buchbinder" <adam.buchbinder@gmail.com>,
"Dave Hansen" <dave.hansen@intel.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
"Tim Chen" <tim.c.chen@linux.intel.com>,
"Rik van Riel" <riel@redhat.com>,
"Andi Kleen" <ak@linux.intel.com>, "Jiri Olsa" <jolsa@redhat.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Joerg Roedel" <joro@8bytes.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
"Linux PM list" <linux-pm@vger.kernel.org>,
linux-efi@vger.kernel.org, xen-devel@lists.xenproject.org,
lguest@lists.ozlabs.org, "kvm list" <kvm@vger.kernel.org>,
"Kernel Hardening" <kernel-hardening@lists.openwall.com>
Subject: [kernel-hardening] Re: [PATCH v3 4/4] KVM: VMX: Simplify segment_base
Date: Tue, 21 Feb 2017 05:28:18 -0500 (EST) [thread overview]
Message-ID: <211929849.24027362.1487672898147.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170221080332.GB3125@gmail.com>
> Paolo, how stable, non-rebasing are the KVM tree commits?
Whatever ends in linux-next is stable. I have a separate rebasing branch,
but it's not part of linux-next by design.
> Or should we keep Andy's KVM patches together with the GDT patches? Either
> workflow works for me - it's your call as these are predominantly KVM
> changes.
I'll delay my pull request to Linus a couple days so that I can test
Andy's 6 patches. Then you can just base your branch on Linus's tree.
Paolo
next prev parent reply other threads:[~2017-02-21 10:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 19:42 [kernel-hardening] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size Thomas Garnier
2017-02-14 19:42 ` [kernel-hardening] [PATCH v3 2/4] x86: Remap GDT tables in the Fixmap section Thomas Garnier
2017-02-15 15:37 ` [kernel-hardening] " Boris Ostrovsky
2017-02-15 15:41 ` Thomas Garnier
2017-02-14 19:42 ` [kernel-hardening] [PATCH v3 3/4] x86: Make the GDT remapping read-only on 64-bit Thomas Garnier
2017-02-14 19:42 ` [kernel-hardening] [PATCH v3 4/4] KVM: VMX: Simplify segment_base Thomas Garnier
2017-02-15 3:57 ` [kernel-hardening] " Andy Lutomirski
2017-02-15 15:44 ` Thomas Garnier
2017-02-17 17:49 ` Jim Mattson
2017-02-17 20:11 ` Thomas Garnier
2017-02-17 21:00 ` Jim Mattson
2017-02-17 22:01 ` Thomas Garnier
2017-02-20 16:56 ` Andy Lutomirski
2017-02-20 17:28 ` Thomas Garnier
2017-02-20 17:39 ` Thomas Garnier
2017-02-21 8:03 ` Ingo Molnar
2017-02-21 10:28 ` Paolo Bonzini [this message]
2017-02-22 6:34 ` Ingo Molnar
2017-02-15 13:58 ` [kernel-hardening] Re: [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size Borislav Petkov
2017-02-15 15:40 ` Thomas Garnier
2017-02-15 15:49 ` Borislav Petkov
2017-02-15 21:08 ` Borislav Petkov
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=211929849.24027362.1487672898147.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=adam.buchbinder@gmail.com \
--cc=ak@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=boris.ostrovsky@oracle.com \
--cc=borntraeger@de.ibm.com \
--cc=bp@suse.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@intel.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=he.chen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jikos@kernel.org \
--cc=jmattson@google.com \
--cc=jolsa@redhat.com \
--cc=joro@8bytes.org \
--cc=jpoimboe@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kvm@vger.kernel.org \
--cc=len.brown@intel.com \
--cc=lguest@lists.ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paul.gortmaker@windriver.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=rkrcmar@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=sgruszka@redhat.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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