From: Joerg Roedel <jroedel@suse.de>
To: Hugh Dickins <hughd@google.com>
Cc: gregkh@linuxfoundation.org,
1532533683-5988-4-git-send-email-joro@8bytes.org,
David.Laight@aculab.com, aarcange@redhat.com, acme@kernel.org,
alexander.levin@microsoft.com,
alexander.shishkin@linux.intel.com, aliguori@amazon.com,
boris.ostrovsky@oracle.com, bp@alien8.de, brgerst@gmail.com,
daniel.gruss@iaik.tugraz.at, dave.hansen@intel.com,
dhgutteridge@sympatico.ca, dvlasenk@redhat.com,
eduval@amazon.com, hpa@zytor.com, jgross@suse.com,
jkosina@suse.cz, jolsa@redhat.comjoro@8bytes.org,
jpoimboe@redhat.com, keescook@google.com, linux-mm@kvack.org,
llong@redhat.com, luto@kernel.org, namhyung@kernel.org,
pavel@ucw.cz, peterz@infradead.org, tglx@linutronix.de,
torvalds@linux-foundation.org, will.deacon@arm.com,
stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "x86/kexec: Allocate 8k PGDs for PTI" has been added to the 3.18-stable tree
Date: Mon, 17 Sep 2018 23:09:55 +0200 [thread overview]
Message-ID: <20180917210955.ucnsxd4bem452kxt@suse.de> (raw)
In-Reply-To: <alpine.LSU.2.11.1809171213560.1601@eggly.anvils>
On Mon, Sep 17, 2018 at 12:33:47PM -0700, Hugh Dickins wrote:
> In several of the recent stable trees, I think this will not do any
> actual harm; but it looks as if it will prevent relevant x86-32 configs
> from building on 3.18 (I see no definition of PGD_ALLOCATION_ORDER in
> linux-3.18.y - you preferred not to have any PTI in that tree), and I
> haven't checked whether its definition in older backports will build
> correctly here or not.
Right, thanks for pointing that out. I should have added a Fixes:-tag to
the patch to make clear what the fix it for, sorry for that.
Joerg
prev parent reply other threads:[~2018-09-17 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 9:46 gregkh
2018-09-17 19:33 ` Hugh Dickins
2018-09-17 20:22 ` Greg KH
2018-09-17 21:09 ` Joerg Roedel [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=20180917210955.ucnsxd4bem452kxt@suse.de \
--to=jroedel@suse.de \
--cc=1532533683-5988-4-git-send-email-joro@8bytes.org \
--cc=David.Laight@aculab.com \
--cc=aarcange@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.levin@microsoft.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aliguori@amazon.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=daniel.gruss@iaik.tugraz.at \
--cc=dave.hansen@intel.com \
--cc=dhgutteridge@sympatico.ca \
--cc=dvlasenk@redhat.com \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=jgross@suse.com \
--cc=jkosina@suse.cz \
--cc=jolsa@redhat.comjoro \
/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