Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp4469191ybz; Tue, 28 Apr 2020 11:49:29 -0700 (PDT) X-Google-Smtp-Source: APiQypLo6dJRGBccVJLakgCQegWd/RAzFi8lzpY6zIoRuSThaziHWVnXj1QAWztOszDDpkuC9VaD X-Received: by 2002:aa7:d0d6:: with SMTP id u22mr24540916edo.262.1588099769788; Tue, 28 Apr 2020 11:49:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588099769; cv=none; d=google.com; s=arc-20160816; b=rGyDAAKnUtS9wPbPEXBveKegglGZvDGd2wZoIMoN3ZlV1P16cKtqZcv8lFjfgk6pUi wKcJHZDICToSnJ+YB1lSBNc+8fC7vK6+S02TmiG3Ram2nulgBQxGLuvisbcTySMOPY/9 QOZgtKgPO4Xb4V3aMEyAVTyKFgf5yotvBBOeBb5DagPt7juCamsphUMqULv/VzwMkWnL OtN6stXFZ3MBtXf6j+1DyzG4NWqH+BxEqU/w3gWfqIKBE5masZJX3MBQ/64WRqSVD9R0 N6wwZ6VPMyARNemP/wtQ33YE9l/aQI4hUratkog0Dt2UXXUUK60CFi0G289URiTijFUT Ym0w== 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=mqodircFvuMAK7KEbdZqAVk2auaU1Fhzu8Wh4NrJOnE=; b=dWLTPERmD4TsuKqDV8fQSCIJ6uTwGtwO7LRQAPNhJlHS7KYGeyQQCHCdi1OfFNZckm 0BGI+dGqshzPnvc+1td059Dz0QivZ5RHQd1rONEKF2B7Ub7a3DfOR/g+MqMhy/jwPgp4 pT3aboSoVm8GduPJpwPUm3oyW1u1pmY0+8knBEdecaAowkaQmZw+9oF5KaDhnaC1b/MW cLwov99R+I8dbkMWkWSU1HckF+cC6/gJRtVqx2wmR4SOqRZCgTswOLRsvIIsiX9MLtyb hl180G/A+QAWIr5/ZzjAoG8BgCnbf6ZPcS3YhH3qNEqngsT7SHDmZyzZI5hhbJd8MbBr 6sOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MlEP6quk; 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 g7si2079621edk.195.2020.04.28.11.49.06; Tue, 28 Apr 2020 11:49:29 -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=MlEP6quk; 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 S1731022AbgD1Sp5 (ORCPT + 99 others); Tue, 28 Apr 2020 14:45:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:36400 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731286AbgD1Snp (ORCPT ); Tue, 28 Apr 2020 14:43:45 -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 CD7A9206D6; Tue, 28 Apr 2020 18:43:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588099425; bh=nZOTCztkrvm3VQFpmLiXSlzVzJMlPmcb9EM8YgnLKNc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=MlEP6qukCmabBaIpFrK51+F/SQRszHXzj1fTiGjIMXNYjMuS/XQTI69fhBquEmm1E aBWgg6coBNWvH7MCfZf9NpuISu4vdCZn3SncJD+Lw95Lj8MjhVu3Yye1m4djlTKtYP rYqWezhxACfkZnP5kkJZz9+UI8AiQFjo1AQQjYTI= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Nicolas Pitre Subject: [PATCH 5.4 138/168] vt: dont hardcode the mem allocation upper bound Date: Tue, 28 Apr 2020 20:25:12 +0200 Message-Id: <20200428182249.274231503@linuxfoundation.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20200428182231.704304409@linuxfoundation.org> References: <20200428182231.704304409@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: Nicolas Pitre commit 2717769e204e83e65b8819c5e2ef3e5b6639b270 upstream. The code in vc_do_resize() bounds the memory allocation size to avoid exceeding MAX_ORDER down the kzalloc() call chain and generating a runtime warning triggerable from user space. However, not only is it unwise to use a literal value here, but MAX_ORDER may also be configurable based on CONFIG_FORCE_MAX_ZONEORDER. Let's use KMALLOC_MAX_SIZE instead. Note that prior commit bb1107f7c605 ("mm, slab: make sure that KMALLOC_MAX_SIZE will fit into MAX_ORDER") the KMALLOC_MAX_SIZE value could not be relied upon. Signed-off-by: Nicolas Pitre Cc: # v4.10+ Link: https://lore.kernel.org/r/nycvar.YSQ.7.76.2003281702410.2671@knanqh.ubzr Signed-off-by: Greg Kroah-Hartman --- drivers/tty/vt/vt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/tty/vt/vt.c +++ b/drivers/tty/vt/vt.c @@ -1206,7 +1206,7 @@ static int vc_do_resize(struct tty_struc if (new_cols == vc->vc_cols && new_rows == vc->vc_rows) return 0; - if (new_screen_size > (4 << 20)) + if (new_screen_size > KMALLOC_MAX_SIZE) return -EINVAL; newscreen = kzalloc(new_screen_size, GFP_USER); if (!newscreen)