From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AA152356776 for ; Fri, 22 May 2026 04:30:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779424205; cv=none; b=GOzN17P7ylCL5Bn/26C3XLfol1cW8/0jFWvG1jM+ERgKVEkGIcWDHDEdsmFT3aFNFrnXDPl75WRMaT6nZAvDsldTrCsDn+Po+41Wd1QImNvfyPjjDTXfJxCxHeccsMoeZxkzzGdbU4PwfVw+88d0xS3Z1Xyf1KxyR4242osHhMs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779424205; c=relaxed/simple; bh=pPzqgTzqMqb2faJTO/Jk+BMJjXY0OVSmCxg42t1cSso=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=twd4m43UB1aexSTM7lNLqMo8cf5VSuJ6jbUh9mbri7k7vSSqv3KDTiy1psTDlyL13TWgxWac9AJ6sFDc7xrYXmL551dyDdeEZkCnI+rRVXN3KP3KNS+TYV8uHT5oYNcYBWi7JxofSt8ocCXVNVsLveNB+eShEBhGyjBy4fFwvoY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=UVWci4c7; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="UVWci4c7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8CBE41F00A3D; Fri, 22 May 2026 04:30:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779424201; bh=kRH3K67GuK3qaAdLfALlSLcLWlmIyUaJOM0TMcoyVtc=; h=Subject:From:Date:References:In-Reply-To:To:Cc; b=UVWci4c7tnPIdnoOqrCepYjMr1PCaJvMJ1z1C81ZYI/FYFKHGpv0O03SUvxgDvA5r W0uwfZkhHEDG+bD6xtLtL7BNmbsTiXFJOXQXRvA5v7ueIglgnpApH0wekfDm10e5lh K04WaJ5pUflXpejv2MrfGygNp5y63eDREFaANgf//6/seLXnj6wq5mQP64/Cqc6BaS rgrXFtk29HqKCHZrymSIR3ogiwLhuQD3I9af3HaQmtLZndir8TmMy9MPH1PHijE14x 6LfjyFrL0kj5B4uTE4X0o71R3vM6TblRniRFoId+YWkqXSjQ14SFQ1ZBYWuLcg94sN yrBiVXjNx4BIg== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 197883930E41; Fri, 22 May 2026 04:30:12 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: submit cached data bios before gc_merge GC From: patchwork-bot+f2fs@kernel.org Message-Id: <177942421064.624124.14751961687530588714.git-patchwork-notify@kernel.org> Date: Fri, 22 May 2026 04:30:10 +0000 References: <20260521053050.1785858-1-qiwenjie@xiaomi.com> In-Reply-To: <20260521053050.1785858-1-qiwenjie@xiaomi.com> To: Wenjie Qi Cc: jaegeuk@kernel.org, chao@kernel.org, qiwenjie@xiaomi.com, linux-kernel@vger.kernel.org, ruipengqi3@gmail.com, linux-f2fs-devel@lists.sourceforge.net Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Thu, 21 May 2026 13:30:50 +0800 you wrote: > Commit fefdf0723650 ("f2fs: fix potential deadlock in f2fs_balance_fs()") > added cached DATA bio submission before direct foreground GC in > f2fs_balance_fs(). > > This avoids a deadlock between writeback and GC on cached data folios. > However, when gc_merge is enabled, f2fs_balance_fs() does not execute > foreground GC in the caller. It wakes the background GC thread and waits > for that foreground request to finish. > > [...] Here is the summary with links: - [f2fs-dev] f2fs: submit cached data bios before gc_merge GC https://git.kernel.org/jaegeuk/f2fs/c/cf69827e772c You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html