public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "tip-bot for H. Peter Anvin" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
	tglx@linutronix.de, fengguang.wu@intel.com, hpa@linux.intel.com
Subject: [tip:x86/urgent] x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off
Date: Thu, 13 Feb 2014 07:54:39 -0800	[thread overview]
Message-ID: <tip-f27d7759ad1ff48673831e598d6df4c76b2bcd06@git.kernel.org> (raw)
In-Reply-To: <20140213124550.GA30497@localhost>

Commit-ID:  f27d7759ad1ff48673831e598d6df4c76b2bcd06
Gitweb:     http://git.kernel.org/tip/f27d7759ad1ff48673831e598d6df4c76b2bcd06
Author:     H. Peter Anvin <hpa@linux.intel.com>
AuthorDate: Thu, 13 Feb 2014 07:46:04 -0800
Committer:  H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Thu, 13 Feb 2014 07:50:45 -0800

x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off

If CONFIG_X86_SMAP is disabled, smap_violation() tests for conditions
which are incorrect (as the AC flag doesn't matter), causing spurious
faults.

The dynamic disabling of SMAP (nosmap on the command line) is fine
because it disables X86_FEATURE_SMAP, therefore causing the
static_cpu_has() to return false.

Found by Fengguang Wu's test system.

Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Link: http://lkml.kernel.org/r/20140213124550.GA30497@localhost
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: <stable@vger.kernel.org> # v3.7+
---
 arch/x86/mm/fault.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 9d591c8..4b39bb7 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -1087,12 +1087,14 @@ __do_page_fault(struct pt_regs *regs, unsigned long error_code)
 	if (unlikely(error_code & PF_RSVD))
 		pgtable_bad(regs, error_code, address);
 
+#ifdef CONFIG_X86_SMAP
 	if (static_cpu_has(X86_FEATURE_SMAP)) {
 		if (unlikely(smap_violation(error_code, regs))) {
 			bad_area_nosemaphore(regs, error_code, address);
 			return;
 		}
 	}
+#endif
 
 	/*
 	 * If we're in an interrupt, have no user context or are running

  parent reply	other threads:[~2014-02-13 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 12:45 [qemu64,+smep,+smap] Kernel panic - not syncing: No working init found Fengguang Wu
2014-02-13 14:55 ` H. Peter Anvin
2014-02-13 15:39   ` H. Peter Anvin
2014-02-13 15:51   ` H. Peter Anvin
2014-02-13 15:54 ` [tip:x86/urgent] x86, smap: Don' t enable SMAP if CONFIG_X86_SMAP is disabled tip-bot for H. Peter Anvin
2014-02-13 15:54 ` tip-bot for H. Peter Anvin [this message]
2014-02-13 16:18 ` [tip:x86/urgent] x86, smap: smap_violation() is bogus if CONFIG_X86_SMAP is off tip-bot for H. Peter Anvin
2014-02-13 16:54 ` tip-bot for H. Peter Anvin

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=tip-f27d7759ad1ff48673831e598d6df4c76b2bcd06@git.kernel.org \
    --to=tipbot@zytor.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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