From: <gregkh@suse.de>
To: kay.sievers@vrfy.org, gregkh@suse.de, greg@kroah.com,
linux-kernel@vger.kernel.org
Subject: patch driver-core-devtmpfs-prevent-concurrent-subdirectory-creation-and-removal.patch added to gregkh-2.6 tree
Date: Thu, 29 Oct 2009 12:29:06 -0700 [thread overview]
Message-ID: <1256844546706@kroah.org> (raw)
In-Reply-To: <1256755866.2618.321.camel@yio.site>
This is a note to let you know that I've just added the patch titled
Subject: Driver core: devtmpfs: prevent concurrent subdirectory creation and removal
to my gregkh-2.6 tree. Its filename is
driver-core-devtmpfs-prevent-concurrent-subdirectory-creation-and-removal.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
>From kay.sievers@vrfy.org Thu Oct 29 11:59:28 2009
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Wed, 28 Oct 2009 19:51:06 +0100
Subject: Driver core: devtmpfs: prevent concurrent subdirectory creation and removal
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Message-ID: <1256755866.2618.321.camel@yio.site>
From: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
drivers/base/devtmpfs.c | 26 ++++++++++++++++----------
1 file changed, 16 insertions(+), 10 deletions(-)
--- a/drivers/base/devtmpfs.c
+++ b/drivers/base/devtmpfs.c
@@ -32,6 +32,8 @@ static int dev_mount = 1;
static int dev_mount;
#endif
+static rwlock_t dirlock;
+
static int __init mount_param(char *str)
{
dev_mount = simple_strtoul(str, NULL, 0);
@@ -86,16 +88,12 @@ static int dev_mkdir(const char *name, m
static int create_path(const char *nodepath)
{
- char *path;
struct nameidata nd;
int err = 0;
- path = kstrdup(nodepath, GFP_KERNEL);
- if (!path)
- return -ENOMEM;
-
+ read_lock(&dirlock);
err = vfs_path_lookup(dev_mnt->mnt_root, dev_mnt,
- path, LOOKUP_PARENT, &nd);
+ nodepath, LOOKUP_PARENT, &nd);
if (err == 0) {
struct dentry *dentry;
@@ -107,14 +105,17 @@ static int create_path(const char *nodep
dput(dentry);
}
mutex_unlock(&nd.path.dentry->d_inode->i_mutex);
-
path_put(&nd.path);
} else if (err == -ENOENT) {
+ char *path;
char *s;
/* parent directories do not exist, create them */
+ path = kstrdup(nodepath, GFP_KERNEL);
+ if (!path)
+ return -ENOMEM;
s = path;
- while (1) {
+ for (;;) {
s = strchr(s, '/');
if (!s)
break;
@@ -125,9 +126,10 @@ static int create_path(const char *nodep
s[0] = '/';
s++;
}
+ kfree(path);
}
+ read_unlock(&dirlock);
- kfree(path);
return err;
}
@@ -232,7 +234,8 @@ static int delete_path(const char *nodep
if (!path)
return -ENOMEM;
- while (1) {
+ write_lock(&dirlock);
+ for (;;) {
char *base;
base = strrchr(path, '/');
@@ -243,6 +246,7 @@ static int delete_path(const char *nodep
if (err)
break;
}
+ write_unlock(&dirlock);
kfree(path);
return err;
@@ -358,6 +362,8 @@ int __init devtmpfs_init(void)
int err;
struct vfsmount *mnt;
+ rwlock_init(&dirlock);
+
err = register_filesystem(&dev_fs_type);
if (err) {
printk(KERN_ERR "devtmpfs: unable to register devtmpfs "
prev parent reply other threads:[~2009-10-29 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 18:51 Driver-Core: devtmpfs - prevent concurrent subdirectory creation and removal Kay Sievers
2009-10-29 19:29 ` gregkh [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=1256844546706@kroah.org \
--to=gregkh@suse.de \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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