Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2171883ybm; Thu, 23 May 2019 12:32:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqzEFkL2rzZBDC540fHPvEjbNxbpHRGn7IPLDQLwnxEe7MXizKKVk6UVGeBsnFK+UkNd7LAK X-Received: by 2002:a63:a1a:: with SMTP id 26mr99741375pgk.11.1558639945873; Thu, 23 May 2019 12:32:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558639945; cv=none; d=google.com; s=arc-20160816; b=ue+cPSu4dfRZaji0eue7FcXD442cizQ8yEY9mo7xgZN0BBUx595BxJxA4PDZMwRVbr qrKLor+JyZDX9Ew7We2EVh90bd0RKaXD0cSzazyRuFwdHAuMnMCOPegNe9LVgr8phzfM rXaVfb+FIoEiCVBGj4vANVC/3cGQ6DN3oB02n0eIcAkX3qcG1eb9adIX0L7gtH16xMDm OuRmxY0TkcU0M90YNacRMKkFPC93Jv1R99Aisd4COESKtdOEK0Po//EhDVLo0wRrwik7 0Vau/B5+wK9Mcc6GVlL2kSNzI/6N+DzEF5EzZkAVZsoAuBkqUB2G44i9OJb3uLZA+bPy ADmw== 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=QOt+nBOImJgplQjNbikB9PDJCKY19XV0SFxCVdN5BDQ=; b=Bg8FXOksmnIs7vNbWeirxhhl+uSsBw0D+du6d5NiKBi9Cv6nCB/I9MrodPOE8PTqgw XOttdj2FDmGjsoYyK8CeAB64Hf2pER7Wy0rTOhh5L5scX6YI+r+ddW2TIeVvp7UPHBaW mKvgyjJMqWFYVycXvEuI3q69TkMMaME3DzF4NL+CKWVlKcLURINvWD7r1JEuBHm/z423 Hb9vHYjqaGDxVpE850tiWwawNlWmNEYwHqQv5XL/y3s+N75Xp8X2jnWKhGltxmw2bumJ O/jVgUArM3xmGpLeyH0BDUj1VEZKUbfdOZz0ZHNax6ChGaNsW1hWDyaAGhtNJzCaRCvY g+ww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=pA7EMfbs; 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 t5si522730pgv.164.2019.05.23.12.32.10; Thu, 23 May 2019 12:32:25 -0700 (PDT) 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=pA7EMfbs; 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 S2392003AbfEWTbH (ORCPT + 99 others); Thu, 23 May 2019 15:31:07 -0400 Received: from mail.kernel.org ([198.145.29.99]:44750 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403757AbfEWTbE (ORCPT ); Thu, 23 May 2019 15:31:04 -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 4D12F2054F; Thu, 23 May 2019 19:31:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558639863; bh=nzeW2X+X5V2hvChwOFElfChmral2wiPC7L2Eajqvbp8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=pA7EMfbsHctIzouoF7F5JUaxskX/iQ/xDknL8yZxH05T3Sr0DWgrUkARGSmXZql+X WAYEe8ChvaJCPD5hmwG5JiprJ87JkddtLBls3q+FpYJkGf53b0gB2OVdHycbN8fxOw tF2BfTiLJ68sy8RQ1oW8Xuj08FD1nHJYbJvXfBd0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Helen Koike , Mike Snitzer Subject: [PATCH 5.1 104/122] dm init: fix max devices/targets checks Date: Thu, 23 May 2019 21:07:06 +0200 Message-Id: <20190523181719.105819177@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190523181705.091418060@linuxfoundation.org> References: <20190523181705.091418060@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: Helen Koike commit 8e890c1ab1b1e0f765cd8da82c4dee011698a5e8 upstream. dm-init should allow up to DM_MAX_{DEVICES,TARGETS} for devices/targets, and not DM_MAX_{DEVICES,TARGETS} - 1. Fix the checks and also fix the error message when the number of devices is surpassed. Fixes: 6bbc923dfcf57d ("dm: add support to directly boot to a mapped device") Cc: stable@vger.kernel.org Signed-off-by: Helen Koike Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman --- drivers/md/dm-init.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) --- a/drivers/md/dm-init.c +++ b/drivers/md/dm-init.c @@ -160,7 +160,7 @@ static int __init dm_parse_table(struct while (table_entry) { DMDEBUG("parsing table \"%s\"", str); - if (++dev->dmi.target_count >= DM_MAX_TARGETS) { + if (++dev->dmi.target_count > DM_MAX_TARGETS) { DMERR("too many targets %u > %d", dev->dmi.target_count, DM_MAX_TARGETS); return -EINVAL; @@ -242,9 +242,9 @@ static int __init dm_parse_devices(struc return -ENOMEM; list_add_tail(&dev->list, devices); - if (++ndev >= DM_MAX_DEVICES) { - DMERR("too many targets %u > %d", - dev->dmi.target_count, DM_MAX_TARGETS); + if (++ndev > DM_MAX_DEVICES) { + DMERR("too many devices %lu > %d", + ndev, DM_MAX_DEVICES); return -EINVAL; }