From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 ECCCE1386DA for ; Tue, 24 Feb 2026 03:55:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771905344; cv=none; b=A5fDpb2OpKzwbPWBm+P2nMwAtC/Tx/ChDwjivuPSDdQTI7kdWMySQZJRg3q+T+Q80ClG5kPqMsLpb7vizdRltPfl8gjdsWDTwwykY5IjnJnRqfGTI5pA3qNO68boRtZ17rqlc/Z+sP55XfLoyAi6ph+aPB5Sj0Y8qHpPZvPzDzU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771905344; c=relaxed/simple; bh=O+MIarzvf6kjqxVQyd3WMBAO83/rjG8t85W7MzgUUDA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=kW7t20OU5Ps5AhW1xb3yRJZNSQoryEditj17gZZ80uHhQbg6rFEZwhxp0At2sq8dFPCQmI00shah4ql/u8TgG7DokAIxWfC2UB9sBs197pPk7GjLqa8PJnuOUhqj88KyIIINRqjz8sHrJL9heevMqcOvEBiRIdNXKngQMZQ6QoA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ikEl1rCc; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ikEl1rCc" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8B299C116D0; Tue, 24 Feb 2026 03:55:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771905343; bh=O+MIarzvf6kjqxVQyd3WMBAO83/rjG8t85W7MzgUUDA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ikEl1rCcdZ7BbDDefOVqu2uHJiOoTzsFGVam4q+7g20QoxFgDbjLwqudI7rDf4sJ6 bHEzFpIM+SZByrQlr6GBZOyg2AwXPDErGmypBoJuxKZr+vKbbXg1mFjS0acwCTcUPD LH9rbWjopDGSNBnAwluuh37WTYKqwBqp71ziJzyz5S9vvXWnnG0J4BWov1YQnJUkXV Qx0YeqNzyAYh7qWD3lUg16TCxxBm2q7InD5WKZSZ8a9YT5dsFXtvvPISQYmt0fwEMX F0gpb4dwQBlj7H0tTxeGB5Gghvtfexp7fk+y3WRIgp+BceSiPKCiPGdvLH7t5uCbPq FsDBeGL7c6qkg== Date: Tue, 24 Feb 2026 03:55:41 +0000 From: Jaegeuk Kim To: Nanzhe Zhao Cc: Chao Yu , Barry Song <21cnbao@gmail.com>, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to prevent clearing immutable for large folio supported inode Message-ID: References: <20260109024716.12047-1-chao@kernel.org> <2cdd4281-7e37-4dd0-91b1-1ab16ef772aa@kernel.org> <8c13ca69-a08a-41c7-bbef-0a79a5f44f93@kernel.org> <83419982-77ba-4dac-880e-bf59669a006f@126.com> <43f34976.480b.19be98c144d.Coremail.nzzhao@126.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43f34976.480b.19be98c144d.Coremail.nzzhao@126.com> On 01/23, Nanzhe Zhao wrote: > Hi Kim: > At 2026-01-23 07:10:05, "Jaegeuk Kim" wrote: > > > > >Yes, I was hitting some issues when I convert the mapping while inode is alive. > >So, for now, we should set it in f2fs_iget() only. > > > > What about using mapping_set_xxx functions in f2fs_new_inode then? How can we guarantee this will be a read-only file? > It maybe be a bit odd to me that we create a immutable file but we can > only get large folios for this inode when the inode is evicted and get > by f2fs_iget again, not get large folios by the first place. > > Thanks, > Nanzhe Zhao