Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3026031pxj; Mon, 17 May 2021 15:54:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyh2w6r0a5Zgg/Ceyau1uuPbVjdLT8Dd3NJbMZcihDV3nms13qhEmC8IbGjTKJq+BS7A6Gh X-Received: by 2002:a92:4b08:: with SMTP id m8mr1629123ilg.183.1621292096236; Mon, 17 May 2021 15:54:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621292096; cv=none; d=google.com; s=arc-20160816; b=R9XmOYuetr2TAKkxTqNtpnBYLjw39xGUO6IaYNkBdrYruXB8PW/IXpT6bkGwbVU1DZ iRjfSLZI/ZKNfyXcETFj/HTFUjCmHM5D1a66UsUkY2v/c7WC9ArqmR0wDzM974yOisAp jbZOPilptW/oryK+jpBr9C6YSKgwZ8txYuqhOsL40ZxJcD7XBptbey2FV3lZvQ9nxvKQ c+d7rUTNqK+sujJ0VkZK1UvhYdTzI+Gs3qhoYmdR6Apef98BREQskqx67xceoijHCLUY 3mcjueXPHeEDgnMcsq0XZ9YlCkR8I/nb9LFMhneY7e6XoNeQSNI28HFdQNpc+XXP0rRq wYfQ== 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=LXIQA1+pFZau0ik9VsUg31KuZqqQQoa6XQsGMa0R94M=; b=NOfZsnNjitkH1TrRDEwmz3GMAgln8ErQ8HGzNca42bQmy5GqCnSeoAOl2QcqduMQqL GaZ5w7xfyPH+dCGfjz7O7KV93+7qpVRXgAkODaxycwUNDdLH0BnWSSRDffBAoDPycM2x rjfOC+BApoPYz6nMeNWY55artu1alx4bB8Ym1Ggzc0elmhz/oojOUEaG5Pxhvt+h2zoZ LUsxcQDdzha8AH3VE6XmAiKp5hIHB7ErsoI1YmMfGwAIA3VeVMIJZnuBgv0jNBAypebL 42Y57ApkJnsa+anZjOxxWfYFgNeq+MT2mi+D731miTlvsByYdTGDxwSl2iGNqKulwHz4 cZvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=Y7l9Nnpx; 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 p10si1258996ilq.156.2021.05.17.15.54.20; Mon, 17 May 2021 15:54:56 -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=Y7l9Nnpx; 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 S236977AbhEQORP (ORCPT + 99 others); Mon, 17 May 2021 10:17:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:46604 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239029AbhEQOOp (ORCPT ); Mon, 17 May 2021 10:14:45 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id D2E0B613EB; Mon, 17 May 2021 14:09:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1621260544; bh=h93cDi0tSDIouVks4MJEb6aFe8DUvxTonnQZVJuzNPA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Y7l9NnpxlvJN5RpJgaWeHGUkgPT9H4J8N2ArRM8bze2YvyA9ClS/HL/H9oQYb00fY 2UM6Vd+VoP2KB+IHRemtgtO9latUhqDFdgM84vwid0t9+RMDtlHAzTomW6l79zR+JG jiJt9ZDQGTCurr9A9BB8LyJQ1jvSVz/V13sFIyjY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chao Yu , Jaegeuk Kim , Sasha Levin Subject: [PATCH 5.12 129/363] f2fs: fix panic during f2fs_resize_fs() Date: Mon, 17 May 2021 15:59:55 +0200 Message-Id: <20210517140306.983407908@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210517140302.508966430@linuxfoundation.org> References: <20210517140302.508966430@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: Chao Yu [ Upstream commit 3ab0598e6d860ef49d029943ba80f627c15c15d6 ] 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 Signed-off-by: Jaegeuk Kim Signed-off-by: Sasha Levin --- 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.30.2