summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorDave Jones <davej@codemonkey.org.uk>2016-10-14 14:26:24 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2016-10-14 11:36:59 -0700
commit496063426dece3f47e21f9f3387205d6ca03bd2a (patch)
tree9c02ece6548b4f5ec443ec8b6be18384750b7e75 /include
parente9f8f48bcac6f6dd37ad89ad63d1d1a497332313 (diff)
downloadop-kernel-dev-496063426dece3f47e21f9f3387205d6ca03bd2a.zip
op-kernel-dev-496063426dece3f47e21f9f3387205d6ca03bd2a.tar.gz
pkeys: Remove easily triggered WARN
This easy-to-trigger warning shows up instantly when running Trinity on a kernel with CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS disabled. At most this should have been a printk, but the -EINVAL alone should be more than adequate indicator that something isn't available. Signed-off-by: Dave Jones <davej@codemonkey.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include')
-rw-r--r--include/linux/pkeys.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/pkeys.h b/include/linux/pkeys.h
index e4c08c1..a1bacf1 100644
--- a/include/linux/pkeys.h
+++ b/include/linux/pkeys.h
@@ -25,7 +25,6 @@ static inline int mm_pkey_alloc(struct mm_struct *mm)
static inline int mm_pkey_free(struct mm_struct *mm, int pkey)
{
- WARN_ONCE(1, "free of protection key when disabled");
return -EINVAL;
}
OpenPOWER on IntegriCloud