Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp538212ybz; Wed, 22 Apr 2020 03:14:35 -0700 (PDT) X-Google-Smtp-Source: APiQypI9+LtaoUwpnQnrjqKqB3Oo5gPRRhk6SjnjuF3obb0brP1/rmXjIxE1MXDTqGICtiLF+oGK X-Received: by 2002:a05:6402:b4c:: with SMTP id bx12mr15943470edb.247.1587550474795; Wed, 22 Apr 2020 03:14:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587550474; cv=none; d=google.com; s=arc-20160816; b=rVFzmMJvJQ073K3229P8k/X3k8Z1dCSO/VUjRpkeZhnYGWXKgKH6SdT3g5V9s9Nvlr LEc98h1oxNeQrpMxfBH4q/fjbZ02mG57yPPL+xxm1DPCgKYJeDUKDY6HWpc2K1+ZT8ui zldcX5QvXUYEp1/MPp4voeSXJiaAcdIONH0oFC4EGUp8KGuTzQG615x7oEudjxLXd730 bhde7+IE7geQZ392o9HYG5SDBRDg8Y5lKBLfevaOfMnG6LECs3MdFxEnkfhtzx0rbUgL F5p5RHBvNWOYiMcnQUzRVedlcrFt4TGrOwTozmDkxojogk1BaEIFlZFJe3dhhhkOqBnF W1hA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=cPgiaB1Orjmm7UCtOj0iD4n6fMljMRlMegsI+EpfIO4=; b=bg4tDuJe1aEiaEtGmCihoho9GTGrD5XbcCKg5SuNeY/4sK7Yg4HGK30D0RvnpHc7Ux CJS8rriqH5jXwj49Z9dyK2gHnTHtzM5dJXaBnSJivnDfY7nxg7VXvE9W6ox7bsxsoGxZ TerNf7oCef3QJPtQSMqFLdKIHzSVLxLlBR1KTH2Cd61iTT5SHxNbC8jIW/YBdaIUCXGU 8rirQ/OajAMwkgjNnClFIfXg4VfVn/vdHp8Su+QyZopkmJxmBUQGUedJyxOFMElm0+ID ZSrRg28H5eFzjPrH0eHSlR7jgXlVuEKYyWJ58D/9hYi7/AeILNi7rj+pOCPnqdo3Mavx ZTcw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=y6jBgjfW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o9si3292027ejr.224.2020.04.22.03.14.12; Wed, 22 Apr 2020 03:14:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=y6jBgjfW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728968AbgDVKKP (ORCPT + 99 others); Wed, 22 Apr 2020 06:10:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:38748 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728955AbgDVKKK (ORCPT ); Wed, 22 Apr 2020 06:10:10 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (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 130D12077D; Wed, 22 Apr 2020 10:10:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587550209; bh=s2KdDNJtF0qnO4d32B5YxCq8JiwYZ0+8BfvcQJBlUoM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=y6jBgjfW/pC+cCl0J1iPBHsmVCaDkxyJPjlYKZM1WENMCEE21+IVa4xPiCFuzDTph dbJiyed0eFCWIJzfeunEMIH5UOVMCxIouVcKNizWbD9Dg0NHqkPDFYkduQHXoU0+8k 1rFk4FUjqJcVqrAgiXMFf6YwjowCD02Sak1I5ivQ= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Eric Biggers , Yang Xu , Jarkko Sakkinen Subject: [PATCH 4.14 051/199] KEYS: reaching the keys quotas correctly Date: Wed, 22 Apr 2020 11:56:17 +0200 Message-Id: <20200422095103.301623069@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200422095057.806111593@linuxfoundation.org> References: <20200422095057.806111593@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Yang Xu commit 2e356101e72ab1361821b3af024d64877d9a798d upstream. Currently, when we add a new user key, the calltrace as below: add_key() key_create_or_update() key_alloc() __key_instantiate_and_link generic_key_instantiate key_payload_reserve ...... Since commit a08bf91ce28e ("KEYS: allow reaching the keys quotas exactly"), we can reach max bytes/keys in key_alloc, but we forget to remove this limit when we reserver space for payload in key_payload_reserve. So we can only reach max keys but not max bytes when having delta between plen and type->def_datalen. Remove this limit when instantiating the key, so we can keep consistent with key_alloc. Also, fix the similar problem in keyctl_chown_key(). Fixes: 0b77f5bfb45c ("keys: make the keyring quotas controllable through /proc/sys") Fixes: a08bf91ce28e ("KEYS: allow reaching the keys quotas exactly") Cc: stable@vger.kernel.org # 5.0.x Cc: Eric Biggers Signed-off-by: Yang Xu Reviewed-by: Jarkko Sakkinen Reviewed-by: Eric Biggers Signed-off-by: Jarkko Sakkinen Signed-off-by: Greg Kroah-Hartman --- security/keys/key.c | 2 +- security/keys/keyctl.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) --- a/security/keys/key.c +++ b/security/keys/key.c @@ -383,7 +383,7 @@ int key_payload_reserve(struct key *key, spin_lock(&key->user->lock); if (delta > 0 && - (key->user->qnbytes + delta >= maxbytes || + (key->user->qnbytes + delta > maxbytes || key->user->qnbytes + delta < key->user->qnbytes)) { ret = -EDQUOT; } --- a/security/keys/keyctl.c +++ b/security/keys/keyctl.c @@ -882,8 +882,8 @@ long keyctl_chown_key(key_serial_t id, u key_quota_root_maxbytes : key_quota_maxbytes; spin_lock(&newowner->lock); - if (newowner->qnkeys + 1 >= maxkeys || - newowner->qnbytes + key->quotalen >= maxbytes || + if (newowner->qnkeys + 1 > maxkeys || + newowner->qnbytes + key->quotalen > maxbytes || newowner->qnbytes + key->quotalen < newowner->qnbytes) goto quota_overrun;