Received: by 2002:ac0:b08d:0:0:0:0:0 with SMTP id l13csp4898941imc; Mon, 25 Feb 2019 13:13:56 -0800 (PST) X-Google-Smtp-Source: AHgI3IZkCp3bsg5ys4QAUiZLFVNhUZzvAiEApzReq/woClmZ6HJW9WjzAqc543eAhV90uwp7BERD X-Received: by 2002:a62:6ec3:: with SMTP id j186mr22997800pfc.89.1551129236304; Mon, 25 Feb 2019 13:13:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551129236; cv=none; d=google.com; s=arc-20160816; b=MMZTP2iUvpLv6HSpYALEtqgNTD+Dr6cMvpvQ/joh7UMxwHkLsh60tUNDTDor+jWfbp HEiZ/NJ2/dlYLbgYAV96w3Y9DuV7j6ZLfq6L6KF2kZoAuyhJe1WGD+Vyp8rjUQ0xxNzQ uEjqRhtfuKeYyPUe+NoOpoQoxdWNPCO/dTLnQSKB4d6qKxmtdjF5zY4ZAuYc3wGMia+c iRcMF717nhc38SSdgHa6P/XAAM+DKM8gaEHt9QSpKk+mLLh6m78Jkbx/DRQq/5yWSwqQ VGsCNG12cUPcHwH3tZO8p/L4KasjTB4rfCp1NFIwdTHYLvLKnzeOQBtWTV8PqTKQ0v2j C27w== 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=GHzjIYIZ4iIvcdzqpFBF5P1aCMXvazIBUDBcXwmOpqQ=; b=rx/djt0hu9yL58NxQRG+kWl/1NAng1WwirvLa45gfe0qBu+cTZCyX3TJXT8CyrBqG5 QwXkB0NSdz/uxOxCdsfgczz3nE0WgJLKZ9Y/L8LAxu0RZLZc0cIvM3HUI/BWVl1VMQhv snxQd8Ui+2wGmzUaScmp9BZ5SxEbOTst+Hqqq5Z4vHLg0QeKEMBaYdHyDiyYvkT4qWED bhBrAcEHE2whUvvY5rfS8tTWeYHSE8v7teILQXGP7gSy3uUl0Lx5AMOGwC5CGqj5T6E0 iZ+aOkxfu5RI0VVIEMZSl1g/9FeEVRznq/RTJlF/z0uph5R753k5PdcyF/71m5me5ohb /9cA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="soR/AkP+"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v10si10357587plp.424.2019.02.25.13.13.41; Mon, 25 Feb 2019 13:13:56 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="soR/AkP+"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728757AbfBYVNF (ORCPT + 99 others); Mon, 25 Feb 2019 16:13:05 -0500 Received: from mail.kernel.org ([198.145.29.99]:43526 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728692AbfBYVNE (ORCPT ); Mon, 25 Feb 2019 16:13:04 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.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 14CE7213A2; Mon, 25 Feb 2019 21:13:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551129183; bh=AD9rEdsTUzUx5WOCq3BRpVa6wwAgCjX3wV94uB8u75M=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=soR/AkP+E7QtPwViG5LD6UxFGR8V5FBeVHzQa5NwUzIjdDLNqJ42SXCKy27Sp6L53 rjxh/qIszZRfZLXsnAhVLvRtVahQVOr5doyPunHeMUyVAsN/a3SznhWRYCTibhNi+u hyrUmxRRAGH0cNRd2B/xn/Bzbm/1qgBiBUCNj8aw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Eric Biggers , David Howells , James Morris Subject: [PATCH 4.9 06/63] KEYS: allow reaching the keys quotas exactly Date: Mon, 25 Feb 2019 22:11:06 +0100 Message-Id: <20190225195036.211333261@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190225195035.713274200@linuxfoundation.org> References: <20190225195035.713274200@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore 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 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Eric Biggers commit a08bf91ce28ed3ae7b6fef35d843fef8dc8c2cd9 upstream. If the sysctl 'kernel.keys.maxkeys' is set to some number n, then actually users can only add up to 'n - 1' keys. Likewise for 'kernel.keys.maxbytes' and the root_* versions of these sysctls. But these sysctls are apparently supposed to be *maximums*, as per their names and all documentation I could find -- the keyrings(7) man page, Documentation/security/keys/core.rst, and all the mentions of EDQUOT meaning that the key quota was *exceeded* (as opposed to reached). Thus, fix the code to allow reaching the quotas exactly. Fixes: 0b77f5bfb45c ("keys: make the keyring quotas controllable through /proc/sys") Cc: stable@vger.kernel.org Signed-off-by: Eric Biggers Signed-off-by: David Howells Signed-off-by: James Morris Signed-off-by: Greg Kroah-Hartman --- security/keys/key.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/security/keys/key.c +++ b/security/keys/key.c @@ -264,8 +264,8 @@ struct key *key_alloc(struct key_type *t spin_lock(&user->lock); if (!(flags & KEY_ALLOC_QUOTA_OVERRUN)) { - if (user->qnkeys + 1 >= maxkeys || - user->qnbytes + quotalen >= maxbytes || + if (user->qnkeys + 1 > maxkeys || + user->qnbytes + quotalen > maxbytes || user->qnbytes + quotalen < user->qnbytes) goto no_quota; }