From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FSL_HELO_FAKE,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DCA75C43387 for ; Thu, 10 Jan 2019 20:28:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AA86A2173B for ; Thu, 10 Jan 2019 20:28:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547152105; bh=v7BamkvMj612/BO0TfiS1g6TOqGh0bBpKBK6sdtqV0I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=RbzLc/pUYE/j6kEFYD/rs94DYX0ZRn0/VqTz5gFBamBd6u/MB9PeIJ0FjedCxMl57 DwmBvuyPiqA3e7ilH2XlA+a5GBHdEqEs+j6o4W5jwfpbgy+deJltvO0RrOG8CORz/i VFkDy8nFp0501QsZAA9rtGFDnvtOmnc+sFm3Fkc0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729094AbfAJU2Z (ORCPT ); Thu, 10 Jan 2019 15:28:25 -0500 Received: from mail.kernel.org ([198.145.29.99]:57590 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727665AbfAJU2Z (ORCPT ); Thu, 10 Jan 2019 15:28:25 -0500 Received: from gmail.com (unknown [104.132.1.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 13B6F213F2; Thu, 10 Jan 2019 20:28:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547152104; bh=v7BamkvMj612/BO0TfiS1g6TOqGh0bBpKBK6sdtqV0I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uZz1Ac3H3ogNbnEvhvwsttDbEr+UiOHGxHkpDCILiKS2eOs+KQx/yMg175ihVHnwu UaoYpr8QWDSOWrMunqSipgP1341uQJ543ydyh15QKYOeKYeNsuibDzzTzK3rY1au4J P7xfAIFilPMVMuIvAsK0k5cGG9yBe2jJ10dJAoi8= Date: Thu, 10 Jan 2019 12:28:22 -0800 From: Eric Biggers To: keyrings@vger.kernel.org, David Howells Cc: linux-security-module@vger.kernel.org Subject: Re: [PATCH RESEND] KEYS: remove CONFIG_KEYS_COMPAT Message-ID: <20190110202822.GC149637@gmail.com> References: <20181115005238.70971-1-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181115005238.70971-1-ebiggers@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On Wed, Nov 14, 2018 at 04:52:38PM -0800, Eric Biggers wrote: > From: Eric Biggers > > KEYS_COMPAT now always takes the value of COMPAT && KEYS. But the > security/keys/ directory is only compiled if KEYS is enabled, so in > practice KEYS_COMPAT is the same as COMPAT. Therefore, remove the > unnecessary KEYS_COMPAT and just use COMPAT directly. > > (Also remove an outdated comment from compat.c.) > > Signed-off-by: Eric Biggers > --- > security/keys/Kconfig | 4 ---- > security/keys/Makefile | 2 +- > security/keys/compat.c | 5 ----- > security/keys/internal.h | 4 ++-- > 4 files changed, 3 insertions(+), 12 deletions(-) > > diff --git a/security/keys/Kconfig b/security/keys/Kconfig > index 6462e6654ccf4..e115d691d9776 100644 > --- a/security/keys/Kconfig > +++ b/security/keys/Kconfig > @@ -20,10 +20,6 @@ config KEYS > > If you are unsure as to whether this is required, answer N. > > -config KEYS_COMPAT > - def_bool y > - depends on COMPAT && KEYS > - > config PERSISTENT_KEYRINGS > bool "Enable register of persistent per-UID keyrings" > depends on KEYS > diff --git a/security/keys/Makefile b/security/keys/Makefile > index 9cef54064f608..c694458d9a46c 100644 > --- a/security/keys/Makefile > +++ b/security/keys/Makefile > @@ -17,7 +17,7 @@ obj-y := \ > request_key_auth.o \ > user_defined.o > compat-obj-$(CONFIG_KEY_DH_OPERATIONS) += compat_dh.o > -obj-$(CONFIG_KEYS_COMPAT) += compat.o $(compat-obj-y) > +obj-$(CONFIG_COMPAT) += compat.o $(compat-obj-y) > obj-$(CONFIG_PROC_FS) += proc.o > obj-$(CONFIG_SYSCTL) += sysctl.o > obj-$(CONFIG_PERSISTENT_KEYRINGS) += persistent.o > diff --git a/security/keys/compat.c b/security/keys/compat.c > index 9482df601dc33..f22527e88e3d5 100644 > --- a/security/keys/compat.c > +++ b/security/keys/compat.c > @@ -50,11 +50,6 @@ static long compat_keyctl_instantiate_key_iov( > > /* > * The key control system call, 32-bit compatibility version for 64-bit archs > - * > - * This should only be called if the 64-bit arch uses weird pointers in 32-bit > - * mode or doesn't guarantee that the top 32-bits of the argument registers on > - * taking a 32-bit syscall are zero. If you can, you should call sys_keyctl() > - * directly. > */ > COMPAT_SYSCALL_DEFINE5(keyctl, u32, option, > u32, arg2, u32, arg3, u32, arg4, u32, arg5) > diff --git a/security/keys/internal.h b/security/keys/internal.h > index 74cb0ff42fedb..d1836e5d670cb 100644 > --- a/security/keys/internal.h > +++ b/security/keys/internal.h > @@ -272,7 +272,7 @@ extern long keyctl_dh_compute(struct keyctl_dh_params __user *, char __user *, > size_t, struct keyctl_kdf_params __user *); > extern long __keyctl_dh_compute(struct keyctl_dh_params __user *, char __user *, > size_t, struct keyctl_kdf_params *); > -#ifdef CONFIG_KEYS_COMPAT > +#ifdef CONFIG_COMPAT > extern long compat_keyctl_dh_compute(struct keyctl_dh_params __user *params, > char __user *buffer, size_t buflen, > struct compat_keyctl_kdf_params __user *kdf); > @@ -287,7 +287,7 @@ static inline long keyctl_dh_compute(struct keyctl_dh_params __user *params, > return -EOPNOTSUPP; > } > > -#ifdef CONFIG_KEYS_COMPAT > +#ifdef CONFIG_COMPAT > static inline long compat_keyctl_dh_compute( > struct keyctl_dh_params __user *params, > char __user *buffer, size_t buflen, > -- > 2.19.1.930.g4563a0d9d0-goog > Ping.