From: Chris Wright <chrisw@osdl.org>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm1: nameif causes oops
Date: Thu, 13 May 2004 11:12:07 -0700 [thread overview]
Message-ID: <20040513111207.A22989@build.pdx.osdl.net> (raw)
In-Reply-To: <20040513172849.GA2188@middle.of.nowhere>; from thunder7@xs4all.nl on Thu, May 13, 2004 at 07:28:49PM +0200
* Jurriaan (thunder7@xs4all.nl) wrote:
> In my untainted 2.6.6-mm1 kernel, I see an oops (the one with the turtle
> graphics) when booting, caused by the usage of nameif (which renames
> ethernet interfaces from 'eth0' to 'adsl' for example).
This has been reported a few other times and Maneesh Soni <maneesh@in.ibm.com>
posted a patch already. I added it below.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
ok it is sysfs related and because of the backing store patches from me.
And here is the fix. Hope this solves your problem.
Thanks
Maneesh
o Fix sysfs_rename_dir(). The sysfs_lookup() does not hash
negative dentries so just hash it before calling d_move
fs/sysfs/dir.c | 1 +
1 files changed, 1 insertion(+)
diff -puN fs/sysfs/dir.c~sysfs-backing-store-sysfs_rename_dir-fix fs/sysfs/dir.c
--- linux-2.6.6-mm1/fs/sysfs/dir.c~sysfs-backing-store-sysfs_rename_dir-fix 2004-10-06 15:21:37.000000000 +0530
+++ linux-2.6.6-mm1-maneesh/fs/sysfs/dir.c 2004-10-06 15:22:03.000000000 +0530
@@ -314,6 +314,7 @@ void sysfs_rename_dir(struct kobject * k
new_dentry = sysfs_get_dentry(parent, new_name);
if (!IS_ERR(new_dentry)) {
if (!new_dentry->d_inode) {
+ d_add(new_dentry, NULL);
d_move(kobj->dentry, new_dentry);
kobject_set_name(kobj,new_name);
}
prev parent reply other threads:[~2004-05-13 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 17:28 Jurriaan
2004-05-13 18:06 ` Valdis.Kletnieks
2004-05-13 18:12 ` Chris Wright [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=20040513111207.A22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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®