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 1497D1DED5B for ; Tue, 11 Aug 2026 07:17:23 +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=1786432645; cv=none; b=TrXIGxvsTRaBHBp06ZXg3JqffKtkOOHbSZ5OIy4BzaCeKiSQA8gbv7nacpv4Msxgs8HyC958oNsfrVURtAPVPwJmzBCLg+7qX6uu6Fs+ND4etI9GXJngbzcAr/kY4VyPte0GfIwM4Er/Vv534lMmF0fJlpjE53bDXlPafYpq2Nk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786432645; c=relaxed/simple; bh=FTCyUe2MLfpbA+nS8TJTQNm3ZwKVNEPK0hnuLiCdNOg=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=AInWebVnhhAaQQRuAWS3NhlGmTfl9YTHP3I9z83BgWqiKBlWmNWOR/HorTyP9nfUuVOfmxpGpu/aQLpLTfO4FL00dnW9/6p/qARFa4mpNzMXqICcnjJrIlJZMo+kCTqr0Qv9WqaiTSXHCjQg0bu4/07JAxiNc6iif7P5+FdA+Aw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=MdFc1/1v; 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="MdFc1/1v" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7A3C71F000E9; Tue, 11 Aug 2026 07:17:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786432643; bh=FTCyUe2MLfpbA+nS8TJTQNm3ZwKVNEPK0hnuLiCdNOg=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=MdFc1/1vOJDdpOjXSJ9naxGBPBfgXOMAHnLHeYjxNemQQlpxX+dWBGl7Y6LIfdZQd C5lKdzGux5KkCdpMq5U9p24O891ydubNru573UxVRENDiWaT5qBlOH7dUQXfdkIWXj jiR9f3/htHtgtVxo1AlI8aut4j8dSBfWEshFz7Hl+xeFwETXj9CkAz2vi7L8ANqs+X H1/+HKOkOyYVtF15WIXm8KM+t7Bha0iDDItY8YfdSEHfBV6mC9XtlymyUwXffbl3zh 3HQ6s6Cg95k3YwKge+PlQfTKxzXOnFJ/84N07Pbd6u1ORJqXR3c0ZAb7ELvuMyfkqD 4pOvZxxNIuGmA== Message-ID: <770d2faf-6523-4528-8325-95c9375ec2fd@kernel.org> Date: Tue, 11 Aug 2026 15:17:20 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: chao@kernel.org, jaegeuk@kernel.org, stable@kernel.org, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH v4 2/2] f2fs: fix to zero post-EOF data when extending file size To: Zhiguo Niu References: <20260809011914.565936-1-chao@kernel.org> <20260809011914.565936-2-chao@kernel.org> Content-Language: en-US From: Chao Yu In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 8/10/26 16:52, Zhiguo Niu wrote: > Chao Yu via Linux-f2fs-devel >> When extending file size (e.g. via truncate, fallocate, or write) across an >> unaligned EOF boundary, we need to ensure that post-EOF data in the partial >> page is zeroed out in pagecache and marked dirty, meanwhile, tagging the inode >> with FI_ZERO_POST_EOF, so that following checkpoint() and fsync() can persist > Hi Chao, > It looks like this version doesn't have this flag "FI_ZERO_POST_EOF"？ Thanks for catching this, fixed in v5. Thanks, > thanks!