Commit f573bbc7 authored by Dave Jones's avatar Dave Jones Committed by Thomas Gleixner

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: default avatarDave Jones <davej@codemonkey.org.uk>
Acked-by: default avatarDave Hansen <dave.hansen@linux.intel.com>
Cc: linux-arch@vger.kernel.org
Cc: arnd@arndb.de
Cc: linux-api@vger.kernel.org
Cc: linux-mm@kvack.org
Cc: luto@kernel.org
Cc: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org
Cc: mgorman@techsingularity.net
Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
parent 6679dac5
...@@ -25,7 +25,6 @@ static inline int mm_pkey_alloc(struct mm_struct *mm) ...@@ -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) static inline int mm_pkey_free(struct mm_struct *mm, int pkey)
{ {
WARN_ONCE(1, "free of protection key when disabled");
return -EINVAL; return -EINVAL;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment