Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp233235pxb; Sat, 20 Feb 2021 01:39:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJzSQTbCjYVoPux5mboCMIVHDMdy+KXav3RpwY7IjCicAHEjfWblv2Ko3FC1xeLgMfaG2GVZ X-Received: by 2002:a17:906:5298:: with SMTP id c24mr12652325ejm.175.1613813985189; Sat, 20 Feb 2021 01:39:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613813985; cv=none; d=google.com; s=arc-20160816; b=AnzoWDfM29RWVmlI+7W+tzu3WedxsmrSNNSE49EerW7283T+YWP23yjvK6bSRcgdra rhL63dhM0XRettx1pxEFrhBxb/9yXMHejWHVw1FvaM1eoJ6Nf4PfG60ECuWqp3qj0dPn SFAWFJEK3pVxs7qV38SEUJ9VZ1ELDAoNyPidl6c2VOP2myVhVUBxtkwH+CLFA/jaU97k ZTiH7vscv0TCbrjBFMu/D5XI778ethTG3/qnt8sYB4i08VH2CuhWU7pUaI+e+RHV3oSi EvzqEstsQ2HC9Vk1D0Br7wLbQK94K9EinupoScYQL3DhDcyCzs60P0TKJLfKklxm4Why 58XQ== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=Zafii94NULn0362N5yv+tj8AXCFTcHJKEwKo4m99SmQ=; b=mK1HsW5cPTtoKpEG1hgdvR6GScn79MOkccADvzgsX6BqM+N5nOG5GmyJD7hHJW3bo6 jbyed+ag8WACuowun8ke6AJPX3pgtnGMO0pIe1HBqp0zjXpF/wBQYbkoEODWMnm4e2/Q yKcvtY5Tq3Io1Wm7mbIyFHCwx8VyXkaH2aOR2YGeDCO9+Q/y/LxBz8gnk0Nrf61NcWZ8 sFSAqB6wfeCsNWj8AED1q6RvhRv2oMmb/5R9YOeEJqavxHe5CCUmDkzG0AG1vY6sXEMV CbZlj3fkTujlIBo6/iM5mcA6h4YIVVNqdCF/3wwUnGjQtzdBZA2vWUq5BfV8GOXYh5pd 3UDg== ARC-Authentication-Results: i=1; mx.google.com; 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 v8si7650660edc.382.2021.02.20.01.39.22; Sat, 20 Feb 2021 01:39:45 -0800 (PST) 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; 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 S229734AbhBTJgu (ORCPT + 99 others); Sat, 20 Feb 2021 04:36:50 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:12930 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229543AbhBTJgr (ORCPT ); Sat, 20 Feb 2021 04:36:47 -0500 Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.58]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4DjNZR21CWzjPMh; Sat, 20 Feb 2021 17:34:39 +0800 (CST) Received: from szvp000203569.huawei.com (10.120.216.130) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.498.0; Sat, 20 Feb 2021 17:35:44 +0800 From: Chao Yu To: CC: , , , Chao Yu Subject: [PATCH 2/2] f2fs: fix panic during f2fs_resize_fs() Date: Sat, 20 Feb 2021 17:35:41 +0800 Message-ID: <20210220093541.63899-2-yuchao0@huawei.com> X-Mailer: git-send-email 2.29.2 In-Reply-To: <20210220093541.63899-1-yuchao0@huawei.com> References: <20210220093541.63899-1-yuchao0@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.120.216.130] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org f2fs_resize_fs() hangs in below callstack with testcase: - mkfs 16GB image & mount image - dd 8GB fileA - dd 8GB fileB - sync - rm fileA - sync - resize filesystem to 8GB kernel BUG at segment.c:2484! Call Trace: allocate_segment_by_default+0x92/0xf0 [f2fs] f2fs_allocate_data_block+0x44b/0x7e0 [f2fs] do_write_page+0x5a/0x110 [f2fs] f2fs_outplace_write_data+0x55/0x100 [f2fs] f2fs_do_write_data_page+0x392/0x850 [f2fs] move_data_page+0x233/0x320 [f2fs] do_garbage_collect+0x14d9/0x1660 [f2fs] free_segment_range+0x1f7/0x310 [f2fs] f2fs_resize_fs+0x118/0x330 [f2fs] __f2fs_ioctl+0x487/0x3680 [f2fs] __x64_sys_ioctl+0x8e/0xd0 do_syscall_64+0x33/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xa9 The root cause is we forgot to check that whether we have enough space in resized filesystem to store all valid blocks in before-resizing filesystem, then allocator will run out-of-space during block migration in free_segment_range(). Fixes: b4b10061ef98 ("f2fs: refactor resize_fs to avoid meta updates in progress") Signed-off-by: Chao Yu --- fs/f2fs/gc.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index b3af76340026..86ba8ed0b8a7 100644 --- a/fs/f2fs/gc.c +++ b/fs/f2fs/gc.c @@ -1977,7 +1977,20 @@ int f2fs_resize_fs(struct f2fs_sb_info *sbi, __u64 block_count) /* stop CP to protect MAIN_SEC in free_segment_range */ f2fs_lock_op(sbi); + + spin_lock(&sbi->stat_lock); + if (shrunk_blocks + valid_user_blocks(sbi) + + sbi->current_reserved_blocks + sbi->unusable_block_count + + F2FS_OPTION(sbi).root_reserved_blocks > sbi->user_block_count) + err = -ENOSPC; + spin_unlock(&sbi->stat_lock); + + if (err) + goto out_unlock; + err = free_segment_range(sbi, secs, true); + +out_unlock: f2fs_unlock_op(sbi); up_write(&sbi->gc_lock); if (err) -- 2.29.2