From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brian Gerst <brgerst@gmail.com>,
David Laight <David.Laight@aculab.com>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH PTI v3 00/10] Clean up pgd handling and fix VSYSCALL and LDT
Date: Tue, 12 Dec 2017 17:14:58 +0100 [thread overview]
Message-ID: <6e628271-37d4-01aa-9fc8-ac3cccf38457@suse.com> (raw)
In-Reply-To: <20171212161315.ij6zkwlim6w5q5dd@pd.tnic>
On 12/12/17 17:13, Borislav Petkov wrote:
> On Tue, Dec 12, 2017 at 07:58:07AM -0800, Andy Lutomirski wrote:
>> Ugh, the whole send-email process exploded due to Cc:
>> stable@vger.kernel.org # 4.14. I stripped the # 4.14 and it's okay
>> now.
>
> In the future, strip the whole CC: stable directly. Although git
> send-email with --suppress-cc is kinda clumsy for that... or I haven't
> figured it out properly.
>
Using
Cc: <stable@vger.kernel.org> # 4.14
works for me.
Juergen
next prev parent reply other threads:[~2017-12-12 16:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 23:40 [PATCH PTI v3 00/10] Clean up pgd handling and fix VSYSCALL and LDT Andy Lutomirski
2017-12-12 10:09 ` Ingo Molnar
2017-12-12 15:58 ` Andy Lutomirski
2017-12-12 16:13 ` Borislav Petkov
2017-12-12 16:14 ` Juergen Gross [this message]
2017-12-12 16:20 ` Borislav Petkov
2017-12-12 15:56 ` [PATCH PTI v3 01/10] x86/espfix/64: Fix espfix double-fault handling on 5-level systems Andy Lutomirski
2017-12-12 17:18 ` Kirill A. Shutemov
2017-12-15 18:34 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 02/10] x86/pti: Vastly simplify pgd synchronization Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 03/10] x86/pti/64: Fix ESPFIX64 user mapping Andy Lutomirski
2017-12-13 13:12 ` Kirill A. Shutemov
2017-12-13 17:01 ` Andy Lutomirski
2017-12-14 14:10 ` Kirill A. Shutemov
2017-12-14 16:18 ` Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 04/10] Revert "x86/mm/pti: Disable native VSYSCALL" Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 05/10] x86/vsyscall/64: Explicitly set _PAGE_USER in the pagetable hierarchy Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 06/10] x86/vsyscall/64: Warn and fail vsyscall emulation in NATIVE mode Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 07/10] x86/pti: Map the vsyscall page if needed Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 08/10] x86/mm/64: Improve the memory map documentation Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 09/10] x86/mm/64: Make a full PGD-entry size hole in the memory map Andy Lutomirski
2017-12-13 13:17 ` Kirill A. Shutemov
2017-12-13 17:04 ` Andy Lutomirski
2017-12-12 15:56 ` [PATCH PTI v3 10/10] x86/pti: Put the LDT in its own PGD if PTI is on Andy Lutomirski
2017-12-15 22:54 ` Thomas Gleixner
2017-12-16 0:39 ` Thomas Gleixner
2017-12-16 6:41 ` Andy Lutomirski
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=6e628271-37d4-01aa-9fc8-ac3cccf38457@suse.com \
--to=jgross@suse.com \
--cc=David.Laight@aculab.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).