From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] OCFS2: unhash all dentries on a inode.
Date: Mon, 22 Sep 2008 21:47:08 -0700 [thread overview]
Message-ID: <48D874CC.1020402@oracle.com> (raw)
In-Reply-To: <48D84BBF.5060503@oracle.com>
If so, won't that be a bug?
wengang wang wrote:
> Sunil,
>
> d_prune_aliases() unhashes dentries that has 0 reference count,
> dentries with non-zero ref count won't be unhashed.
> My code unhashes all no matter there reference counts are 0 or not.
>
> regards,
> wengang.
>
> Sunil Mushran wrote:
>> NAK.
>>
>> I fail to understand your logic. The code you've added is pretty
>> much what d_prune_aliases() does (the call you have deleted).
>>
>> wangang wang wrote:
>>> In ocfs2_process_delete_request(), we should unhash all dentries on
>>> the inode.
>>> --not only the ones with 0 referrence count. so that it's possible
>>> for dput()
>>> to drop the stale inode.
>>>
>>> the patch is against 1.2 svn.
>>>
>>> Signed-off-by: Wengang wang <wen.gang.wang@oracle.com>
>>> --
>>>
>>> Index: fs/ocfs2/vote.c
>>> ===================================================================
>>> --- fs/ocfs2/vote.c (revision 3101)
>>> +++ fs/ocfs2/vote.c (working copy)
>>> @@ -176,6 +176,7 @@
>>> int deleting_node)
>>> {
>>> int response = OCFS2_RESPONSE_BUSY;
>>> + struct list_head *tmp, *head;
>>>
>>> mlog(0, "DELETE vote on inode %lu, read lnk_cnt = %u, slot =
>>> %d\n",
>>> inode->i_ino, inode->i_nlink, *orphaned_slot);
>>> @@ -253,9 +254,19 @@
>>> ocfs2_mark_inode_remotely_deleted(inode, deleting_node);
>>> spin_unlock(&OCFS2_I(inode)->ip_lock);
>>>
>>> - /* Not sure this is necessary anymore. */
>>> - d_prune_aliases(inode);
>>> + /* unhash all dentries on this inode */
>>> + spin_lock(&dcache_lock);
>>> + head = &inode->i_dentry;
>>> + tmp = head;
>>>
>>> + while ((tmp = tmp->next) != head) {
>>> + struct dentry *dentry = list_entry(tmp, struct dentry,
>>> d_alias);
>>> + spin_lock(&dentry->d_lock);
>>> + __d_drop(dentry);
>>> + spin_unlock(&dentry->d_lock);
>>> + }
>>> + spin_unlock(&dcache_lock);
>>> +
>>> /* If we get here, then we're voting 'yes', so commit the
>>> * delete on our side. */
>>> response = OCFS2_RESPONSE_OK;
>>>
>>> _______________________________________________
>>> Ocfs2-devel mailing list
>>> Ocfs2-devel at oss.oracle.com
>>> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>>>
>>
>
next prev parent reply other threads:[~2008-09-23 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 9:48 [Ocfs2-devel] [PATCH 1/1] OCFS2: unhash all dentries on a inode wangang wang
2008-09-22 21:46 ` Sunil Mushran
2008-09-23 1:51 ` wengang wang
2008-09-23 4:47 ` Sunil Mushran [this message]
2008-09-23 5:27 ` wengang wang
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=48D874CC.1020402@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.