From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: Nick Piggin <npiggin@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Important for fs devs: rcu-walk merged upstream
Date: Mon, 10 Jan 2011 23:38:47 +0900 [thread overview]
Message-ID: <22537.1294670327@jrobl> (raw)
In-Reply-To: <AANLkTimBrR1LkVHOxZA=UUmKsnxfsFLr9z_AhXUHQ_7N@mail.gmail.com>
Nick Piggin:
> This is a big and complex change by any measure, so
> please don't be afraid to ask for help or clarification. I'd
> also really like to be able to update documentation
> based on questions from fs maintainers (in and out of
> tree) who are trying to follow it and bring their code up to
> speed.
Question about what d_lock protects.
Can we skip d_lock when we access d_inode and d_name during its parent
i_mutex is held?
Should these BUG_ON be placed after d_lock?
void dentry_update_name_case(struct dentry *dentry, struct qstr *name)
{
BUG_ON(!mutex_is_locked(&dentry->d_inode->i_mutex));
BUG_ON(dentry->d_name.len != name->len); /* d_lookup gives this */
spin_lock(&dentry->d_lock);
:::
J. R. Okajima
next prev parent reply other threads:[~2011-01-10 14:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 2:54 Important for fs devs: rcu-walk merged upstream Nick Piggin
2011-01-08 9:10 ` Marco Stornelli
2011-01-11 9:57 ` Nick Piggin
2011-01-11 9:57 ` Nick Piggin
2011-01-11 11:08 ` Miklos Szeredi
2011-01-10 14:38 ` J. R. Okajima [this message]
2011-01-11 12:57 ` Nick Piggin
2011-01-11 12:57 ` Nick Piggin
2011-01-11 1:08 ` Joel Becker
2011-01-11 13:06 ` Nick Piggin
2011-01-11 13:06 ` Nick Piggin
2011-01-13 14:58 ` Miklos Szeredi
2011-01-13 16:18 ` Miklos Szeredi
2011-01-14 1:21 ` Nick Piggin
2011-01-14 1:21 ` Nick Piggin
2011-01-14 8:45 ` Miklos Szeredi
2011-01-14 8:45 ` Miklos Szeredi
2011-01-14 8:52 ` Nick Piggin
2011-01-14 8:52 ` Nick Piggin
2011-01-14 9:38 ` Miklos Szeredi
2011-01-14 9:38 ` Miklos Szeredi
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=22537.1294670327@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.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.