From: bilal.amarni@gmail.com (Bilal Amarni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: enable CONFIG_KEYS_COMPAT in Kconfig
Date: Mon, 23 Jan 2017 18:03:12 +0100 [thread overview]
Message-ID: <1485190992-86476-1-git-send-email-bilal.amarni@gmail.com> (raw)
Currently in 32-bit userspace calling the keyctl syscall returns an ENOSYS error.
This makes sure the compatibility wrapper is registered.
Signed-off-by: Bilal Amarni <bilal.amarni@gmail.com>
---
arch/arm64/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 1117421..d76f70b 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -1030,6 +1030,10 @@ config SYSVIPC_COMPAT
def_bool y
depends on COMPAT && SYSVIPC
+config KEYS_COMPAT
+ def_bool y
+ depends on COMPAT && KEYS
+
endmenu
menu "Power management options"
--
2.7.2
next reply other threads:[~2017-01-23 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 17:03 Bilal Amarni [this message]
2017-01-25 21:22 ` [PATCH] ARM64: enable CONFIG_KEYS_COMPAT in Kconfig Arnd Bergmann
2017-01-26 11:49 ` [PATCH] security/keys: add CONFIG_KEYS_COMPAT to Kconfig Bilal Amarni
2017-01-26 12:55 ` kbuild test robot
2017-01-26 13:27 ` Bilal Amarni
2017-02-08 13:01 ` Bilal Amarni
2017-02-08 13:25 ` Arnd Bergmann
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=1485190992-86476-1-git-send-email-bilal.amarni@gmail.com \
--to=bilal.amarni@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).