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 0BEC034D4FE for ; Tue, 14 Jul 2026 03:00:32 +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=1783998034; cv=none; b=i8CRPj7ffVZLdDPkAedwZ7ALAALwTxHLIXUV02uKT9tibWFS3EvE4ve51nfiihIJZ6ulOQXe1AW/uOViLcMaTCcONAatRJhYAQ/V/WpDLdA2NAcHjoGZPor11RIbgpvt31/79ZWDQEA124vc5xkbdwvOPijP0u1xhaQmScLqCNI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783998034; c=relaxed/simple; bh=bvbp3w6l6uSLSovvpdwHi5KoPRXa1JhS4oioNdKYFDM=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=F5f1KO3ibkcPPC/+StcxHaoP6OK9ZnPwmFgPA8t2HL/4cHQ0MiBDaKKUyRZ29iloqhea3U5OQLOAsZW+ixD86m5s2Qh5osEJQ05s0kN6nd51le/I3CwxyVojvhAa8zOD8dJqpYyKzch8mKV16pq46uaxQPSqJ1V3nUrKiYiA+18= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=G4v6PmXJ; 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="G4v6PmXJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 997BC1F000E9; Tue, 14 Jul 2026 03:00:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783998032; bh=zChAImWOrlDN51gcoddbdazwdae3tP6/MAG5aFHKXeI=; h=Subject:From:Date:References:In-Reply-To:To:Cc; b=G4v6PmXJCDJwnX6/hwmigLLg1xAapqTTBAu80i0vuAAlJbODU398uwrDQrgK6/h66 ZdNlh/R+NZivJuqcKj27NVluxBTmSogc5SLArhv/cBWi0xbeQEA7d9zstgljrVq3c6 NNYglqlTqHay6hxtJtmWkqtxDTuaBmt9Ucy3YUvZqTzwRW3hs3oluaVbgnTyYEUNDd JyLjlrEzgHgpLCz7I6c9BpQchpRtOrz+A35uMNFE94QqsEds5vq86qZo0UIYGb4Mq6 1Nr9uIS89Ffvnp1ksXXdTKswKPEkw/XXHTmGlKJTGm+ApIcprb3RWzeN8aBQv3MItn nYhBHRl0AvlgA== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id D0A213924FB7; Tue, 14 Jul 2026 03:00:08 +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: fix to avoid potential section-unaligned pinfile From: patchwork-bot+f2fs@kernel.org Message-Id: <178399800738.2939750.5347430287438781500.git-patchwork-notify@kernel.org> Date: Tue, 14 Jul 2026 03:00:07 +0000 References: <20260629114918.224537-1-chao@kernel.org> In-Reply-To: <20260629114918.224537-1-chao@kernel.org> To: Chao Yu Cc: jaegeuk@kernel.org, stable@kernel.org, daehojeong@google.com, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 29 Jun 2026 11:49:18 +0000 you wrote: > Blocks of pinfile may not aligned to section size due to wrong use > on pinfile, result in heavy overhead of GC, let avoid this by > adding additional check condition in f2fs_setattr(). > > - truncate -s 8mb pinfile > : random checkpoint may persist filesize w/ inode > - fallocate -o 0 -l 8mb pinfile > - f2fs_fallocate > - f2fs_expand_inode_data > - f2fs_allocate_pinning_section > - f2fs_map_blocks > - f2fs_map_lock > - __allocate_data_block > - file_need_truncate > : w/ FADVISE_TRUNC_BIT, we can expect unaligned mapping can be > truncated while open() if f2fs is not umount abnormally > - f2fs_map_unlock > : following f2fs checkpoint and sudden power-cut > > [...] Here is the summary with links: - [f2fs-dev] f2fs: fix to avoid potential section-unaligned pinfile https://git.kernel.org/jaegeuk/f2fs/c/bf4272cef5ec You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html