From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Mark Tinguely <mark.tinguely@oracle.com>,
Mateusz Guzik <mjguzik@gmail.com>,
ocfs2-devel@lists.linux.dev
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
josef@toxicpanda.com, jlbec@evilplan.org, mark@fasheh.com,
brauner@kernel.org, willy@infradead.org, david@fromorbit.com
Subject: Re: [External] : [PATCH] ocfs2: retire ocfs2_drop_inode() and I_WILL_FREE usage
Date: Mon, 8 Sep 2025 09:33:59 +0800 [thread overview]
Message-ID: <4432e4ee-96c5-424d-b2af-6f4553b30057@linux.alibaba.com> (raw)
In-Reply-To: <f3671198-5231-41cf-b0bc-d1280992947a@oracle.com>
On 2025/9/5 00:15, Mark Tinguely wrote:
> On 9/4/25 10:42 AM, Mateusz Guzik wrote:
>> This postpones the writeout to ocfs2_evict_inode(), which I'm told is
>> fine (tm).
>>
>> The intent is to retire the I_WILL_FREE flag.
>>
>> Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
>> ---
>>
>> ACHTUNG: only compile-time tested. Need an ocfs2 person to ack it.
>>
>> btw grep shows comments referencing ocfs2_drop_inode() which are already
>> stale on the stock kernel, I opted to not touch them.
>>
>> This ties into an effort to remove the I_WILL_FREE flag, unblocking
>> other work. If accepted would be probably best taken through vfs
>> branches with said work, see https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/log/?h=vfs-6.18.inode.refcount.preliminaries__;!!ACWV5N9M2RV99hQ!OLwk8DVo7uvC-Pd6XVTiUCgP6MUDMKBMEyuV27h_yPGXOjaq078-kMdC9ILFoYQh-4WX93yb0nMfBDFFY_0$
>>
>> fs/ocfs2/inode.c | 23 ++---------------------
>> fs/ocfs2/inode.h | 1 -
>> fs/ocfs2/ocfs2_trace.h | 2 --
>> fs/ocfs2/super.c | 2 +-
>> 4 files changed, 3 insertions(+), 25 deletions(-)
>>
>> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
>> index 6c4f78f473fb..5f4a2cbc505d 100644
>> --- a/fs/ocfs2/inode.c
>> +++ b/fs/ocfs2/inode.c
>> @@ -1290,6 +1290,8 @@ static void ocfs2_clear_inode(struct inode *inode)
>> void ocfs2_evict_inode(struct inode *inode)
>> {
>> + write_inode_now(inode, 1);
>> +
>> if (!inode->i_nlink ||
>> (OCFS2_I(inode)->ip_flags & OCFS2_INODE_MAYBE_ORPHANED)) {
>> ocfs2_delete_inode(inode);
>> @@ -1299,27 +1301,6 @@ void ocfs2_evict_inode(struct inode *inode)
>> ocfs2_clear_inode(inode);
>> }
>> -/* Called under inode_lock, with no more references on the
>> - * struct inode, so it's safe here to check the flags field
>> - * and to manipulate i_nlink without any other locks. */
>> -int ocfs2_drop_inode(struct inode *inode)
>> -{
>> - struct ocfs2_inode_info *oi = OCFS2_I(inode);
>> -
>> - trace_ocfs2_drop_inode((unsigned long long)oi->ip_blkno,
>> - inode->i_nlink, oi->ip_flags);
>> -
>> - assert_spin_locked(&inode->i_lock);
>> - inode->i_state |= I_WILL_FREE;
>> - spin_unlock(&inode->i_lock);
>> - write_inode_now(inode, 1);
>> - spin_lock(&inode->i_lock);
>> - WARN_ON(inode->i_state & I_NEW);
>> - inode->i_state &= ~I_WILL_FREE;
>> -
>> - return 1;
>> -}
>> -
>> /*
>> * This is called from our getattr.
>> */
>> diff --git a/fs/ocfs2/inode.h b/fs/ocfs2/inode.h
>> index accf03d4765e..07bd838e7843 100644
>> --- a/fs/ocfs2/inode.h
>> +++ b/fs/ocfs2/inode.h
>> @@ -116,7 +116,6 @@ static inline struct ocfs2_caching_info *INODE_CACHE(struct inode *inode)
>> }
>> void ocfs2_evict_inode(struct inode *inode);
>> -int ocfs2_drop_inode(struct inode *inode);
>> /* Flags for ocfs2_iget() */
>> #define OCFS2_FI_FLAG_SYSFILE 0x1
>> diff --git a/fs/ocfs2/ocfs2_trace.h b/fs/ocfs2/ocfs2_trace.h
>> index 54ed1495de9a..4b32fb5658ad 100644
>> --- a/fs/ocfs2/ocfs2_trace.h
>> +++ b/fs/ocfs2/ocfs2_trace.h
>> @@ -1569,8 +1569,6 @@ DEFINE_OCFS2_ULL_ULL_UINT_EVENT(ocfs2_delete_inode);
>> DEFINE_OCFS2_ULL_UINT_EVENT(ocfs2_clear_inode);
>> -DEFINE_OCFS2_ULL_UINT_UINT_EVENT(ocfs2_drop_inode);
>> -
>> TRACE_EVENT(ocfs2_inode_revalidate,
>> TP_PROTO(void *inode, unsigned long long ino,
>> unsigned int flags),
>> diff --git a/fs/ocfs2/super.c b/fs/ocfs2/super.c
>> index 53daa4482406..e4b0d25f4869 100644
>> --- a/fs/ocfs2/super.c
>> +++ b/fs/ocfs2/super.c
>> @@ -129,7 +129,7 @@ static const struct super_operations ocfs2_sops = {
>> .statfs = ocfs2_statfs,
>> .alloc_inode = ocfs2_alloc_inode,
>> .free_inode = ocfs2_free_inode,
>> - .drop_inode = ocfs2_drop_inode,
>> + .drop_inode = generic_delete_inode,
>> .evict_inode = ocfs2_evict_inode,
>> .sync_fs = ocfs2_sync_fs,
>> .put_super = ocfs2_put_super,
>
>
> I agree, fileystems should not use I_FREEING/I_WILL_FREE.
> Doing the sync write_inode_now() should be fine in ocfs_evict_inode().
>
> Question is ocfs_drop_inode. In commit 513e2dae9422:
> ocfs2: flush inode data to disk and free inode when i_count becomes zero
> the return of 1 drops immediate to fix a memory caching issue.
> Shouldn't .drop_inode() still return 1?
>
I think commit 513e2dae9422 only expected the write_inode_now() is
determinately called in iput_final(), no matter drop_inode() return 0 or
1.
Thanks,
Joseph
next prev parent reply other threads:[~2025-09-08 1:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <766vdz3ecpm7hv4sp5r3uu4ezggm532ng7fdklb2nrupz6minz@qcws3ufabnjp>
2025-09-04 15:42 ` Mateusz Guzik
2025-09-04 16:15 ` [External] : " Mark Tinguely
2025-09-04 16:22 ` Mateusz Guzik
2025-09-08 1:51 ` Joseph Qi
2025-09-08 10:23 ` Jan Kara
2025-09-08 12:41 ` Joseph Qi
2025-09-08 13:54 ` Jan Kara
2025-09-08 15:39 ` Mateusz Guzik
2025-09-09 9:51 ` Jan Kara
2025-09-09 9:52 ` Mateusz Guzik
2025-09-09 9:57 ` Mateusz Guzik
2025-09-15 12:21 ` Christian Brauner
2025-09-09 1:23 ` Joseph Qi
2025-09-09 9:49 ` Jan Kara
2025-09-09 9:58 ` Joseph Qi
2025-09-15 12:21 ` Christian Brauner
2025-09-08 1:33 ` Joseph Qi [this message]
2025-09-05 13:29 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4432e4ee-96c5-424d-b2af-6f4553b30057@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.tinguely@oracle.com \
--cc=mark@fasheh.com \
--cc=mjguzik@gmail.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®