public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Jerome de Vivie <jerome.devivie@free.fr>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: changing d_parent
Date: Mon, 19 May 2003 08:07:11 +0200	[thread overview]
Message-ID: <20030519060711.GA944@vagabond> (raw)
In-Reply-To: <3EC7C605.DB4BA3ED@free.fr>

On Sun, May 18, 2003 at 07:42:29PM +0200, Jerome de Vivie wrote:
> 
> I would like to change the "d_parent" field of a dentry. This is for
> shrinking entry equivalent to a "./" in my filesystem namespace.
> 
> The dentry has just been allocated and has no child. I'm new to the 
> dcache and i would like to know if thoses lines are is safe:
> 
>     spin_lock(&dcache_lock);
>     list_del(&dentry->d_child);
>     dput(dentry->d_parent);
>     dentry->d_parent = dget(newparent);
>     list_add(&dentry->d_child, &newparent->d_subdirs);
>     spin_unlock(&dcache_lock);

One thing that comes to mind, the dentry must not be hashed and you need
to hash it at some point (d_rehash()) (IIRC it does not work on hashed
dentries).

Another thing is, that dput may lock dcache_lock, so it must be only
called after you release it.

Also note the difference of dget and dget_locked. None of them locks
dcache_lock, but dget only gets a dentry you already hold (remember, you
are not expected to hold dcache_lock), while dget_locked can get
a dentry you just found in child list/hash.

I wonder what you are really doing. You should never ever need to mess
with . and .., since lookup deals with them for you.

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

      parent reply	other threads:[~2003-05-19  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 17:42 changing d_parent Jerome de Vivie
2003-05-19  5:55 ` Maneesh Soni
2003-05-19  6:07 ` Jan Hudec [this message]

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=20030519060711.GA944@vagabond \
    --to=bulb@ucw.cz \
    --cc=jerome.devivie@free.fr \
    --cc=linux-fsdevel@vger.kernel.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