From: Maneesh Soni <maneesh@in.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: "James H. Cloos Jr." <cloos@jhcloos.com>,
linux-kernel@vger.kernel.org, adam@yggdrasil.com,
kernel@kolivas.org
Subject: Re: 2.5.61-mm1
Date: Mon, 17 Feb 2003 17:08:56 +0530 [thread overview]
Message-ID: <20030217113856.GC1112@in.ibm.com> (raw)
In-Reply-To: <20030215162904.6ba8fdc2.akpm@digeo.com>
On Sun, Feb 16, 2003 at 12:31:31AM +0000, Andrew Morton wrote:
> "James H. Cloos Jr." <cloos@jhcloos.com> wrote:
> >
> > I just tried 2.5.61 and 2.5.61-mm1 on a dell inspiron 8100.
> >
> > 2.5.61 is working OK, but -mm1 hung as soon as it tried to exec init.
> > init=/bin/bash showed the same failure.
> >
> > init(8) was able to print out it's first line, announcing its version
> > but then stopped. with init=/bin/bash bash did not output anything.
> >
>
> If you are using devfs then yes, there is a locking problem.
>
> If you are not using devfs then please send me your .config.
>
> Thanks.
Hello Andrew,
The following patch should enable smalldevfs to work with dcache_rcu. The
locking problem is because smalldevfs is written keeping fastwalk
in mind where as dcache_rcu backs out fastwalk code to 2.5.10 level.
Patch is based on 2.5.61-mm1.
Regards,
Maneesh
dcache_rcu-smalldevfs.patch
diff -urN linux-2.5.61-mm1/fs/devfs/base.c linux-2.5.61-mm1-smalldevfs-dcache_rcu/fs/devfs/base.c
--- linux-2.5.61-mm1/fs/devfs/base.c 2003-02-17 12:04:54.000000000 +0530
+++ linux-2.5.61-mm1-smalldevfs-dcache_rcu/fs/devfs/base.c 2003-02-17 12:29:46.000000000 +0530
@@ -60,8 +60,7 @@
memcpy(buf, *path, len);
buf[len] = '\0';
- spin_lock(&dcache_lock);
- err = link_path_walk(buf, nd); /* releases dcache_lock */
+ err = link_path_walk(buf, nd);
if (err)
return err;
@@ -101,14 +100,13 @@
memset(&nd, 0, sizeof(nd));
nd.flags = LOOKUP_PARENT;
- nd.mnt = devfs_vfsmount;
- nd.dentry = dir;
+ nd.mnt = mntget(devfs_vfsmount);
+ nd.dentry = dget(dir);
err = walk_parents_mkdir(&name, &nd, is_dir);
if (err)
return err;
- spin_lock(&dcache_lock);
err = link_path_walk(name, &nd);
if (err)
return err;
@@ -247,10 +245,9 @@
buf[sizeof(buf)-1] = '\0';
memset(&nd, 0, sizeof(nd));
- nd.mnt = devfs_vfsmount;
- nd.dentry = devfs_vfsmount->mnt_sb->s_root;
+ nd.mnt = mntget(devfs_vfsmount);
+ nd.dentry = dget(devfs_vfsmount->mnt_sb->s_root);
- spin_lock(&dcache_lock);
err = link_path_walk(buf, &nd);
if (!err) {
devfs_unregister(nd.dentry);
--
Maneesh Soni
IBM Linux Technology Center,
IBM India Software Lab, Bangalore.
Phone: +91-80-5044999 email: maneesh@in.ibm.com
http://lse.sourceforge.net/
next prev parent reply other threads:[~2003-02-17 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 7:13 2.5.61-mm1 Andrew Morton
2003-02-15 7:25 ` 2.5.61-mm1 Nick Piggin
2003-02-15 11:27 ` 2.5.61-mm1 Con Kolivas
2003-02-15 23:41 ` 2.5.61-mm1 Andrew Morton
2003-02-16 1:03 ` 2.5.61-mm1 Con Kolivas
2003-02-15 14:29 ` 2.5.61-mm1 Ed Tomlinson
2003-02-16 0:12 ` 2.5.61-mm1 James H. Cloos Jr.
2003-02-16 0:29 ` 2.5.61-mm1 Andrew Morton
2003-02-17 11:38 ` Maneesh Soni [this message]
2003-02-17 11:29 ` 2.5.61-mm1 Andrew Morton
2003-02-17 22:44 ` 2.5.61-mm1 Cliff White
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=20030217113856.GC1112@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=adam@yggdrasil.com \
--cc=akpm@digeo.com \
--cc=cloos@jhcloos.com \
--cc=kernel@kolivas.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