public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86/speculation/l1tf: Add assembly guard for xtensa/ia64
Date: Wed, 15 Aug 2018 15:36:58 -0700	[thread overview]
Message-ID: <20180815223658.GA11323@roeck-us.net> (raw)
In-Reply-To: <20180815215646.12653-1-andi@firstfloor.org>

On Wed, Aug 15, 2018 at 02:56:46PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
> 
> The stable backport of the
> 
> x86/speculation/l1tf: Disallow non privileged high MMIO PROT_NONE mappings
> 
> patch for 4.4 and 4.9 put new C code for !__HAVE_ARCH_PFN_MODIFY_ALLOWED
> code outside the assembler ifdef. This breaks the xtensa and ia64
> build as reported by 0day which somehow include this file
> into assembler.
> 
> Just add an #ifdef __ASSEMBLY__ around the new code to fix this.
> 
> This patch is only needed for 4.9 and 4.4 stable, the newer stables
> don't have this problem.
> 
> Fixes: 7c5b42f82c13 ("x86/speculation/l1tf: Disallow non privileged high MMIO PROT_NONE mappings")
> Signed-off-by: Andi Kleen <ak@linux.intel.com>

This should be fixed in the final stable releases.
The problem was caused by a couple of missing backports.

Guenter

      reply	other threads:[~2018-08-15 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 21:56 [PATCH] x86/speculation/l1tf: Add assembly guard for xtensa/ia64 Andi Kleen
2018-08-15 22:36 ` Guenter Roeck [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=20180815223658.GA11323@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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