From: Joel Becker <Joel.Becker@oracle.com>
To: Louis Rilling <louis.rilling@kerlabs.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [BUGFIX][PATCH 1/2] configfs: Prevent userspace from creating new entries under attaching directories
Date: Thu, 3 Jul 2008 14:58:56 -0700 [thread overview]
Message-ID: <20080703215856.GG1502@mail.oracle.com> (raw)
In-Reply-To: <1214503549-15678-2-git-send-email-louis.rilling@kerlabs.com>
On Thu, Jun 26, 2008 at 08:05:48PM +0200, Louis Rilling wrote:
> This commit fixes 1/, tagging new directories with CONFIGFS_USET_CREATING before
> building the inode and instantiating the dentry, and validating the whole
> group+default groups hierarchy in a second pass by clearing
> CONFIGFS_USET_CREATING.
Man, I'm wary of all these in-flight flags. I hope they are all
orthogonal :-)
> mkdir(), symlink(), lookup(), and dir_open() simply return -ENOENT if
> called in (or linking to) a directory tagged with CONFIGFS_USET_CREATING. This
Why not block until the create is done?
> + /*
> + * Fake invisibility if dir belongs to a group/default groups hierarchy
> + * being attached
> + *
> + * This forbids userspace to read/write attributes of items which may
> + * not complete their initialization, since the dentries of the
> + * attributes won't be instantiated.
> + */
int configfs_dirent_is_ready(struct configfs_dirent *sd)
{
int err = 0;
> + spin_lock(&configfs_dirent_lock);
> + if (parent_sd->s_type & CONFIGFS_USET_CREATING)
> + err = -ENOENT;
> + spin_unlock(&configfs_dirent_lock);
return err;
}
Then use is_ready() in the five places you check it ;-) Perhaps
change configfs_validate_dir() to configfs_dir_set_ready(). I do like
the way validate_dir() is coded.
Joel
--
"There are only two ways to live your life. One is as though nothing
is a miracle. The other is as though everything is a miracle."
- Albert Einstein
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2008-07-03 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 18:05 [BUGFIX][PATCH 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-06-26 18:05 ` [BUGFIX][PATCH 1/2] configfs: Prevent userspace from creating new entries under attaching directories Louis Rilling
2008-07-03 21:58 ` Joel Becker [this message]
2008-07-04 11:12 ` [Ocfs2-devel] " Louis Rilling
2008-06-26 18:05 ` [BUGFIX][PATCH 2/2] configfs: Lock new directory inodes before removing on cleanup after failure Louis Rilling
2008-07-03 22:06 ` [Ocfs2-devel] " Joel Becker
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=20080703215856.GG1502@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.rilling@kerlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox