From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@digeo.com
Subject: Re: Patch: linux-2.5.59/fs/devfs shrink
Date: Fri, 17 Jan 2003 21:08:49 -0800 [thread overview]
Message-ID: <200301180508.VAA07511@adam.yggdrasil.com> (raw)
Many thanks to Andrew Morton for a patch to my devfs shrink
that fixes premature unlocking of an inode, eliminates a redundant "if
(err)", and removes an incorrect comment. I'm running with Andrew's
changes now, and I've put up a new diff against 2.5.59 so that
everyone can be up to date, at the following URL.
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/smalldevfs-2.5.59-v9.patch
Just for completeness, here is the URL for devfs_helper (no change):
ftp://ftp.yggdrasil.com/pub/dist/device_control/devfs/devfs_helper-0.2.tar.gz
Also for completeness, I've appended a copy of Andrew's diff.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
devfs/base.c | 11 ++++-------
devfs/fs.c | 0
2 files changed, 4 insertions(+), 7 deletions(-)
diff -puN fs/devfs/base.c~a fs/devfs/base.c
--- 25/fs/devfs/base.c~a 2003-01-17 19:20:17.000000000 -0800
+++ 25-akpm/fs/devfs/base.c 2003-01-17 19:26:29.000000000 -0800
@@ -48,7 +48,6 @@ extern int __init init_devfs_fs(void);
different interface from lookup_create. */
extern struct dentry *lookup_create(struct nameidata *nd, int is_dir);
-/* Called and returns with dcache_lock held. */
static int walk_parents_mkdir(const char **path, struct nameidata *nd,
int is_dir)
{
@@ -78,10 +77,8 @@ static int walk_parents_mkdir(const char
up(&nd->dentry->d_parent->d_inode->i_sem);
- if (err) {
- if (err)
- return err;
- }
+ if (err)
+ return err;
*path += len + 1;
}
@@ -156,7 +153,6 @@ devfs_handle_t devfs_register (devfs_han
goto err_free_devnum;
err = vfs_mknod(parent_inode, dentry, mode, devnum);
- up(&parent_inode->i_sem);
if (!err) {
/* FIXME? Is DEVFS_FL_CURRENT_OWNER useful? Don't we
already set uid and gid to current->fs{uid,gid}? */
@@ -164,8 +160,10 @@ devfs_handle_t devfs_register (devfs_han
dentry->d_inode->i_uid = current->uid;
dentry->d_inode->i_gid = current->gid;
}
+ up(&parent_inode->i_sem);
return dentry;
}
+ up(&parent_inode->i_sem);
dput(dentry);
@@ -259,7 +257,6 @@ void devfs_remove(const char *fmt, ...)
devfs_put(nd.dentry);
}
}
-
EXPORT_SYMBOL(devfs_remove);
int devfs_only(void)
diff -puN fs/devfs/fs.c~a fs/devfs/fs.c
_
next reply other threads:[~2003-01-18 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 5:08 Adam J. Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 3:02 Adam J. Richter
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=200301180508.VAA07511@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=akpm@digeo.com \
--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
all inboxes | Powered by JetHome®