From: David Howells <dhowells@redhat.com>
To: Bilal Amarni <bilal.amarni@gmail.com>
Cc: dhowells@redhat.com, arnd@arndb.de, james.l.morris@oracle.com,
serge@hallyn.com, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] security/keys: add CONFIG_KEYS_COMPAT to Kconfig
Date: Fri, 10 Feb 2017 11:04:34 +0000 [thread overview]
Message-ID: <29042.1486724674@warthog.procyon.org.uk> (raw)
In-Reply-To: <1486674698-67190-1-git-send-email-bilal.amarni@gmail.com>
Bilal Amarni <bilal.amarni@gmail.com> wrote:
> CONFIG_KEYS_COMPAT is defined in arch-specific Kconfigs and is missing for
> several 64-bit architectures : arm64, mips, parisc, tile.
>
> At the moment and for those architectures, calling in 32-bit userspace the
> keyctl syscall would return an ENOSYS error.
>
> This patch moves the CONFIG_KEYS_COMPAT option to security/keys/Kconfig, to
> make sure the compatibility wrapper is registered by default for any 64-bit
> architecture as long as it is configured with CONFIG_COMPAT.
>
> Signed-off-by: Bilal Amarni <bilal.amarni@gmail.com>
Applied.
next prev parent reply other threads:[~2017-02-10 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 21:11 Bilal Amarni
2017-02-10 8:15 ` Arnd Bergmann
2017-02-10 11:04 ` David Howells [this message]
2017-03-29 19:20 ` Eric Biggers
2017-06-03 2:43 ` Eric Biggers
2017-06-03 8:04 ` David Howells
2017-06-05 3:34 ` Eric Biggers
-- strict thread matches above, loose matches on Subject: below --
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=29042.1486724674@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=arnd@arndb.de \
--cc=bilal.amarni@gmail.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
/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
Powered by JetHome