From: Dave Hansen <dave.hansen@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mceier@gmail.com, aaro.koskinen@nokia.com, aarcange@redhat.com,
luto@kernel.org, arjan@linux.intel.com, bp@alien8.de,
dan.j.williams@intel.com, dwmw2@infradead.org,
gregkh@linuxfoundation.org, hughd@google.com,
jpoimboe@redhat.com, jgross@suse.com, keescook@google.com,
torvalds@linux-foundation.org, namit@vmware.com,
peterz@infradead.org
Subject: Re: [PATCH 2/2] x86, pti: fix boot warning from Global-bit setting
Date: Fri, 20 Apr 2018 12:44:47 -0700 [thread overview]
Message-ID: <df7f4b2c-9048-19f5-4817-45d29eec022c@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1804201215170.1683@nanos.tec.linutronix.de>
On 04/20/2018 03:16 AM, Thomas Gleixner wrote:
>> pageattr.c is not friendly when it encounters empty (zero) PTEs. The
>> kernel linear map is exempt from these checks, but kernel text is not.
>> This patch adds the code to also exempt kernel text from these checks.
> Bah. Changelogs should tell the WHY and not the WHAT
>
>> The proximate cause of these warnings was most likely an __init area
>> that spanned a 2MB page boundary that resulted in a "zero" PMD.
> This doesn't make any sense at all.
I've rewritten these changelogs and added some more fixes for this set.
I'll be sending it shortly.
prev parent reply other threads:[~2018-04-20 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:13 [PATCH 1/2] x86, pti: fix boot problems " Dave Hansen
2018-04-17 21:13 ` [PATCH 2/2] x86, pti: fix boot warning " Dave Hansen
2018-04-17 21:56 ` Mariusz Ceier
2018-04-18 11:05 ` kbuild test robot
2018-04-18 12:26 ` kbuild test robot
2018-04-20 10:16 ` Thomas Gleixner
2018-04-20 19:44 ` Dave Hansen [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=df7f4b2c-9048-19f5-4817-45d29eec022c@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=aaro.koskinen@nokia.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mceier@gmail.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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