Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp621959img; Fri, 22 Mar 2019 05:20:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqzD4cfE/MMrx9da8yhzL86oQaYNN8InMAC9svDqg+HK3DA3E2WSycuc3uEOl8yfG60wessB X-Received: by 2002:a65:49c4:: with SMTP id t4mr8631031pgs.421.1553257218779; Fri, 22 Mar 2019 05:20:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553257218; cv=none; d=google.com; s=arc-20160816; b=AVGauak/e4NZOfm832fGXj3n7ARilXgkSvzgYIRB5x4ybG2psg5kNRIasvQurQB6GJ ItRwmXtl+cjfjxexiEX9c2rDSJaXcIkHpKhv5nc7tt+7XuVaDqaQk/Fw2yd0xePDmOhC G8WAoBqm7/4eULBtwhpCBxr4iHSXRx1ev710ut0cZql3tvrAHfALut9fSIsmIqrryB8l gg3tRqZkpTE1Jiqnfss09ISnA013PsIun1G265QO+NG5is8aV44reCz5GU8el7kvjsDy kTsot1k9fnRsq52J9pdMmkbEAPrLzzR+Df0esCUZnRNyl6K7wfUPnvYggUGgnYqXNkpa q6DA== 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=aHHyQh7Qp1kihTWeB966UZ/CZo9JhNCcctNZcIhW1hI=; b=JESbjvaFpMV9vZoAb5eyrJorl8RppoRcLvYIziDnLZdGMv6oWaRx0IheB79wNtHXc/ D9EARdwWxlBLaJFoVj+vlEJbc/2jLZIAX+vHMulNoP39nuJ+XYjD4RGf8ufbzqq5v1IC ppyKxz9qIrTFewh4zePzeN9h48Gqr2dA8i8Z3e8Wte1ZuVOmuLYQuwJR8/Bb3TaH8bWW Et9m2b/UqK5Q7t8hIOa8ZYbJ4T88fooRC0/Y60T6hL/BHZ45KSrS1A6xTN+5pn9tGFYt DsUxA6PWTtzIwZWeVncp+BzZ45t1ar5teJi2z/nxjVUDGJNwMRXMDMNzj6clwLbt9wV4 wVnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=HWd3x4Q+; 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 h3si6441566pfj.137.2019.03.22.05.20.04; Fri, 22 Mar 2019 05:20:18 -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=HWd3x4Q+; 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 S2390482AbfCVMST (ORCPT + 99 others); Fri, 22 Mar 2019 08:18:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:57164 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390465AbfCVMSR (ORCPT ); Fri, 22 Mar 2019 08:18:17 -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 CF5E32083D; Fri, 22 Mar 2019 12:18:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553257096; bh=7Kb4Nzdt5mu11PDTeGB4O/Jye+8sFQfdJJHyufy1iHk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=HWd3x4Q+wx9i1fb86O1t5XAOqLjwXBS6If45QxE+VLZqU3bym2V5lo0n0kvOLS0Os iwYq5TtvbmLcn45LYc4SxEcHH97dPUhC4GdPis2SJMWgWCk0NYy8+cNBTFMAx/jGKi xZ/GZqwUfrfDZNr56O8X8J413J0igswe0gmkM9q8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Jan Kara , Theodore Tso Subject: [PATCH 5.0 123/238] ext4: fix crash during online resizing Date: Fri, 22 Mar 2019 12:15:42 +0100 Message-Id: <20190322111305.777385901@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190322111258.383569278@linuxfoundation.org> References: <20190322111258.383569278@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 5.0-stable review patch. If anyone has any objections, please let me know. ------------------ From: Jan Kara commit f96c3ac8dfc24b4e38fc4c2eba5fea2107b929d1 upstream. When computing maximum size of filesystem possible with given number of group descriptor blocks, we forget to include s_first_data_block into the number of blocks. Thus for filesystems with non-zero s_first_data_block it can happen that computed maximum filesystem size is actually lower than current filesystem size which confuses the code and eventually leads to a BUG_ON in ext4_alloc_group_tables() hitting on flex_gd->count == 0. The problem can be reproduced like: truncate -s 100g /tmp/image mkfs.ext4 -b 1024 -E resize=262144 /tmp/image 32768 mount -t ext4 -o loop /tmp/image /mnt resize2fs /dev/loop0 262145 resize2fs /dev/loop0 300000 Fix the problem by properly including s_first_data_block into the computed number of filesystem blocks. Fixes: 1c6bd7173d66 "ext4: convert file system to meta_bg if needed..." Signed-off-by: Jan Kara Signed-off-by: Theodore Ts'o Cc: stable@vger.kernel.org Signed-off-by: Greg Kroah-Hartman --- fs/ext4/resize.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- a/fs/ext4/resize.c +++ b/fs/ext4/resize.c @@ -1960,7 +1960,8 @@ retry: le16_to_cpu(es->s_reserved_gdt_blocks); n_group = n_desc_blocks * EXT4_DESC_PER_BLOCK(sb); n_blocks_count = (ext4_fsblk_t)n_group * - EXT4_BLOCKS_PER_GROUP(sb); + EXT4_BLOCKS_PER_GROUP(sb) + + le32_to_cpu(es->s_first_data_block); n_group--; /* set to last group number */ }