Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2156553ybm; Thu, 23 May 2019 12:17:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqzaisnrMhGIPWXy+1WmEHy9MOUYpKtkXv9w0fteE45MaXFykNTjleqY7oYnoOy8dSq7b6Ic X-Received: by 2002:a17:90a:7343:: with SMTP id j3mr3417987pjs.84.1558639033457; Thu, 23 May 2019 12:17:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558639033; cv=none; d=google.com; s=arc-20160816; b=pAD81fXVBfh7T93velInhpCf0ksmSqv11hqElOoY4gOF4rCRcgpPAdFA4YYqQ0Z5+v JhyV7aUsLIUMIVRzOZuwDpEddVaMy+MZBepe5vctj6EokZIyD0vngqRu1E9688DbwO7e +81m/T90zyLVOlIJYki/RcIT5Oa8P1RLdJE2WTBZyffLctltiQdQDp+e36S47unueedS I9H6kfxTqZ5GMgP0Ws4xt1lwrh49Fm7C0/oT2bKamn7AEUr0qZPCkrqqV1RHezW6urvG Urgg3rbEzhci5swHxZRMO2MUDStCPSg79NXlwBpHJLW2WDDNp5N7RSJgKR/SGxKtfbbT q9Ag== 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=PA1FVkGOEbZgXAmI4EUOUKmB0+iEZHn9Oyg5hsM5i5Q=; b=UJKHLX9X6PJxbGhAoFswtKcN8itzLFtXDBhUUvgmnPBNJdXEpFcUpuuwCyYaVXSFoO /wezIDX3YttQemPu6DUnJ7sZfxVHtHs8j6bFl2lq9pqCk9hBCHW7TgGAhEEvvpiQaG9C UvLSVh7b8nWe2/oxIfHZ5i0dcA9BiSvf0locw/3WsLjAiL4wpSj2ME7fK2rzJWFrySzh tE8fSFMNJeTPOU0mIgyl+50NrSu5mnhRaO385Moc+xZTVK6qKrN7BaSKgbGjs1rzK1d3 T7bbYnNEu+IMPPSJZ0vr1liWlov74OSu7TQMUURMG+duZ0r7dj2S/oP5JR+wtXRyeu6s alFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=xxbaxBP+; 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 w7si521052ply.279.2019.05.23.12.16.58; Thu, 23 May 2019 12:17:13 -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=xxbaxBP+; 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 S2388663AbfEWTOD (ORCPT + 99 others); Thu, 23 May 2019 15:14:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:47974 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388393AbfEWTOC (ORCPT ); Thu, 23 May 2019 15:14:02 -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 E8DF620863; Thu, 23 May 2019 19:14:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558638841; bh=2ptE7vIvQyhsyXR24RemViMRC03B+p8ztYdpEcbI6Q8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=xxbaxBP+RDej9ari1YbSODmxwpT/hYTrXHcmTIDqsImi2SlNVzGld8SdxbW8OAa3X liVN7nGpCVgLf+/B1iJ6SK7pGDcAZplLJwdpSAO9u92hKT+sXX42Lx66g5TG7Ftxn+ x4+k1Q4/OVLExL3i8WDK84XHfYkZMIsKrMrI0AVc= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Damien Le Moal , Shaun Tancheff , Mike Snitzer Subject: [PATCH 4.14 54/77] dm zoned: Fix zone report handling Date: Thu, 23 May 2019 21:06:12 +0200 Message-Id: <20190523181727.481354761@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190523181719.982121681@linuxfoundation.org> References: <20190523181719.982121681@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: Damien Le Moal commit 7aedf75ff740a98f3683439449cd91c8662d03b2 upstream. The function blkdev_report_zones() returns success even if no zone information is reported (empty report). Empty zone reports can only happen if the report start sector passed exceeds the device capacity. The conditions for this to happen are either a bug in the caller code, or, a change in the device that forced the low level driver to change the device capacity to a value that is lower than the report start sector. This situation includes a failed disk revalidation resulting in the disk capacity being changed to 0. If this change happens while dm-zoned is in its initialization phase executing dmz_init_zones(), this function may enter an infinite loop and hang the system. To avoid this, add a check to disallow empty zone reports and bail out early. Also fix the function dmz_update_zone() to make sure that the report for the requested zone was correctly obtained. Fixes: 3b1a94c88b79 ("dm zoned: drive-managed zoned block device target") Cc: stable@vger.kernel.org Signed-off-by: Damien Le Moal Reviewed-by: Shaun Tancheff Signed-off-by: Damien Le Moal Signed-off-by: Mike Snitzer Signed-off-by: Greg Kroah-Hartman --- drivers/md/dm-zoned-metadata.c | 5 +++++ 1 file changed, 5 insertions(+) --- a/drivers/md/dm-zoned-metadata.c +++ b/drivers/md/dm-zoned-metadata.c @@ -1169,6 +1169,9 @@ static int dmz_init_zones(struct dmz_met goto out; } + if (!nr_blkz) + break; + /* Process report */ for (i = 0; i < nr_blkz; i++) { ret = dmz_init_zone(zmd, zone, &blkz[i]); @@ -1204,6 +1207,8 @@ static int dmz_update_zone(struct dmz_me /* Get zone information from disk */ ret = blkdev_report_zones(zmd->dev->bdev, dmz_start_sect(zmd, zone), &blkz, &nr_blkz, GFP_NOIO); + if (!nr_blkz) + ret = -EIO; if (ret) { dmz_dev_err(zmd->dev, "Get zone %u report failed", dmz_id(zmd, zone));