Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4822825pxj; Wed, 9 Jun 2021 02:43:52 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxiAryx56akFI/CWk/L5yo7sEzYSzESY1TAGMyTDRyoIXxqutJvgrl9ZnBqmGd682FaviMO X-Received: by 2002:a05:6638:151:: with SMTP id y17mr24707327jao.128.1623231831978; Wed, 09 Jun 2021 02:43:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623231831; cv=none; d=google.com; s=arc-20160816; b=Ks4uoR6LTYI7bYYiKEiqbfXnQuzOs4CevpNbi2/ChKLfQWWnzZWVSBUE5JiLAfGxVa FoCGU2zaNIvQu7KZfRqO4gDrR1FZ0VDnCvROIhGHuF/XLKXdJOD9J3MpRMD+29QdBb+1 E/ptlTj2V8s0aUorX5Cdq4jmMzTnHZb4O5hO/clvE/dMa2DxMvWU4Heox57naOh8bY0g 8mYJATKKAlxMEQU1xVqMpAQomgRSA47UGdM3PEb5r8SSV0LvUTIUyyTffk4l2d8JVvIu oVigR77zqHPAJe8nUciYweSdiqMNcOZVpAKwKTUlnAGngAO8NtFcmNSGWqF2ORUgM4UA Oy+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=jnzuiLiaFhV+I+5sur+Xl+o6OwpslBrFrCrappSgWyg=; b=YlltN6RFQokDe7Ai1cL2LvdDivYUXTjkkeKn+jRHk7bITi7v+BdyQKVrYs1Cc/xMWy kVBkifPEOcfFAuLU1ZapiiURo6JAGo+ShetF33sWPmg0JNS8eBcM3kGckHGuYVWpyAvG nFTawDWCXpMKg4OEM57o+eXMru6PDu+d6mYj8+YFjZnnTttbrn+XbmS9SIPRS2KF4Men 2jdlsm516lWkRu62BSs4iKexz+QwGAzqwpC2IVCNGxnnYrNJpHeLCVm4HPI16UhSaeYj w4+uKV5IJk1+9YOOFVAMW3R/jh6EfNlUDAQfEusUP9drVyYzWh3pclsnPRe4mxIy4OJu d+SA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=CrrhHQch; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x1si2741763ilm.32.2021.06.09.02.43.40; Wed, 09 Jun 2021 02:43:51 -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=@linuxfoundation.org header.s=korg header.b=CrrhHQch; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235058AbhFHSlP (ORCPT + 99 others); Tue, 8 Jun 2021 14:41:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:37622 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234922AbhFHSiz (ORCPT ); Tue, 8 Jun 2021 14:38:55 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 8DA5E613AE; Tue, 8 Jun 2021 18:33:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1623177217; bh=4v20Y3cW3crsKshZu1FlBZ5JvWMmOmocwgADLSqD2oE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=CrrhHQchxMxsVSOjMCSQV4Lgry0GMP0tBehCfZpv+ei7laKHfrD+RzI6zusNlSHnV KAE1CvZeDt6FAvjrqq3i8+r3XwLtSDK7Y2JBEBCHy//ulClQrRIHEkUrntHMXHfr+A ieueanXqStV9gNpACJMAM0gKnfuXKauZltnCEVyM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, stable@kernel.org, Ye Bin , Jan Kara , Theodore Tso Subject: [PATCH 4.19 29/58] ext4: fix bug on in ext4_es_cache_extent as ext4_split_extent_at failed Date: Tue, 8 Jun 2021 20:27:10 +0200 Message-Id: <20210608175933.244562632@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210608175932.263480586@linuxfoundation.org> References: <20210608175932.263480586@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ye Bin commit 082cd4ec240b8734a82a89ffb890216ac98fec68 upstream. We got follow bug_on when run fsstress with injecting IO fault: [130747.323114] kernel BUG at fs/ext4/extents_status.c:762! [130747.323117] Internal error: Oops - BUG: 0 [#1] SMP ...... [130747.334329] Call trace: [130747.334553] ext4_es_cache_extent+0x150/0x168 [ext4] [130747.334975] ext4_cache_extents+0x64/0xe8 [ext4] [130747.335368] ext4_find_extent+0x300/0x330 [ext4] [130747.335759] ext4_ext_map_blocks+0x74/0x1178 [ext4] [130747.336179] ext4_map_blocks+0x2f4/0x5f0 [ext4] [130747.336567] ext4_mpage_readpages+0x4a8/0x7a8 [ext4] [130747.336995] ext4_readpage+0x54/0x100 [ext4] [130747.337359] generic_file_buffered_read+0x410/0xae8 [130747.337767] generic_file_read_iter+0x114/0x190 [130747.338152] ext4_file_read_iter+0x5c/0x140 [ext4] [130747.338556] __vfs_read+0x11c/0x188 [130747.338851] vfs_read+0x94/0x150 [130747.339110] ksys_read+0x74/0xf0 This patch's modification is according to Jan Kara's suggestion in: https://patchwork.ozlabs.org/project/linux-ext4/patch/20210428085158.3728201-1-yebin10@huawei.com/ "I see. Now I understand your patch. Honestly, seeing how fragile is trying to fix extent tree after split has failed in the middle, I would probably go even further and make sure we fix the tree properly in case of ENOSPC and EDQUOT (those are easily user triggerable). Anything else indicates a HW problem or fs corruption so I'd rather leave the extent tree as is and don't try to fix it (which also means we will not create overlapping extents)." Cc: stable@kernel.org Signed-off-by: Ye Bin Reviewed-by: Jan Kara Link: https://lore.kernel.org/r/20210506141042.3298679-1-yebin10@huawei.com Signed-off-by: Theodore Ts'o Signed-off-by: Greg Kroah-Hartman --- fs/ext4/extents.c | 43 +++++++++++++++++++++++-------------------- 1 file changed, 23 insertions(+), 20 deletions(-) --- a/fs/ext4/extents.c +++ b/fs/ext4/extents.c @@ -3263,7 +3263,10 @@ static int ext4_split_extent_at(handle_t ext4_ext_mark_unwritten(ex2); err = ext4_ext_insert_extent(handle, inode, ppath, &newex, flags); - if (err == -ENOSPC && (EXT4_EXT_MAY_ZEROOUT & split_flag)) { + if (err != -ENOSPC && err != -EDQUOT) + goto out; + + if (EXT4_EXT_MAY_ZEROOUT & split_flag) { if (split_flag & (EXT4_EXT_DATA_VALID1|EXT4_EXT_DATA_VALID2)) { if (split_flag & EXT4_EXT_DATA_VALID1) { err = ext4_ext_zeroout(inode, ex2); @@ -3289,30 +3292,30 @@ static int ext4_split_extent_at(handle_t ext4_ext_pblock(&orig_ex)); } - if (err) - goto fix_extent_len; - /* update the extent length and mark as initialized */ - ex->ee_len = cpu_to_le16(ee_len); - ext4_ext_try_to_merge(handle, inode, path, ex); - err = ext4_ext_dirty(handle, inode, path + path->p_depth); - if (err) - goto fix_extent_len; - - /* update extent status tree */ - err = ext4_zeroout_es(inode, &zero_ex); - - goto out; - } else if (err) - goto fix_extent_len; - -out: - ext4_ext_show_leaf(inode, path); - return err; + if (!err) { + /* update the extent length and mark as initialized */ + ex->ee_len = cpu_to_le16(ee_len); + ext4_ext_try_to_merge(handle, inode, path, ex); + err = ext4_ext_dirty(handle, inode, path + path->p_depth); + if (!err) + /* update extent status tree */ + err = ext4_zeroout_es(inode, &zero_ex); + /* If we failed at this point, we don't know in which + * state the extent tree exactly is so don't try to fix + * length of the original extent as it may do even more + * damage. + */ + goto out; + } + } fix_extent_len: ex->ee_len = orig_ex.ee_len; ext4_ext_dirty(handle, inode, path + path->p_depth); return err; +out: + ext4_ext_show_leaf(inode, path); + return err; } /*