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 EBD4E489882 for ; Tue, 25 Aug 2026 15:40:58 +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=1787672461; cv=none; b=t7wSzUM77hjQHvEVsI2o7BHogBgwoGcoyPdDw7oFVudgiKRyEnoln0/zunZ3qoRw6UtS3zrXyW1vAkYijjk55KBlDRaaXpSOzIfE6ZaGvYS8J5q7WlscpqvlfWo+xuwAipnlD/8xDvdVv/gP5qgRqLRNeZ31/x7kvVoAgZfoY9M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787672461; c=relaxed/simple; bh=jYg8a17PYYbpONGxrk60QNwgWIjDWS9bNXhiAKtHmsg=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=E0EVRfrDHhm8K5rUs1eoqtJhxrtvTm//FsIK5vtkFS6ElrKOR2HYnarRsbhmH63QR6DZMDB8RXAs0xpImdqT3eIfK9mi8CaFvWWl2sf5liq0hgUOy33O3AcbbP8R4lFr0jZ5yco0XwUk1LqBTt7FSbn3FCLOn/N6a6Tt7A05cDw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=npAlK5DI; 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="npAlK5DI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6CF511F000E9; Tue, 25 Aug 2026 15:40:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787672458; bh=rbJ84W6tWDUKStY1FZU2kjP51571p0eDKeLfqpheWms=; h=Subject:From:Date:References:In-Reply-To:To:Cc; b=npAlK5DIIwnYoThg2RryWtT5VBJDkHyovFZL8u+vmYnO/lF5FqrF61Fz59zdyoYww Cn47VDTIKAOFrv9Ia8gVeKDNTv9GGnFIgvbr8ZLF+x300LHvf96fUJ4pNLS04O/cVm Gra/lI/qGCOVR9Z682r+SLxCtck9rZ5k1BwI/gaw487emW5E7qc35JtO3yZdruAPPi kUvoLZMwyk8wt4UKkigYGnrlUKSipLfHgNp4FcLAaI0e8C5Y+hUUrTTOqUmA0aj7/a 3VXZeUrYzr5zLh/FMG8IKUh8IXszpUc62UflkTqtBR8a182X40C1Briavb+nrwEcdp 3IihdaRYwbz9A== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 93A9E3924FEE; Tue, 25 Aug 2026 15:40:06 +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 v2] f2fs: use adjusted write range after f2fs_write_checks() From: patchwork-bot+f2fs@kernel.org Message-Id: <178767240514.3943858.5716693691312332057.git-patchwork-notify@kernel.org> Date: Tue, 25 Aug 2026 15:40:05 +0000 References: <20260824023231.24616-1-jsjlee1020@gmail.com> In-Reply-To: <20260824023231.24616-1-jsjlee1020@gmail.com> To: Seongjae Jeong Cc: jaegeuk@kernel.org, chao@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, 24 Aug 2026 02:32:31 +0000 you wrote: > generic_write_checks() in f2fs_write_checks() can adjust iocb->ki_pos > for append writes and truncate the iterator to limit the number of bytes > to write. > > In f2fs_file_write_iter(), the pinned-file overwrite check currently > uses the position and count saved before f2fs_write_checks(), so it > can check a range different from the actual write range. > > [...] Here is the summary with links: - [f2fs-dev,v2] f2fs: use adjusted write range after f2fs_write_checks() https://git.kernel.org/jaegeuk/f2fs/c/3b2c5d35cf43 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html