From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: maneesh@in.ibm.com, linux-kernel@vger.kernel.org,
mochel@digitalimplant.org
Subject: Re: problem with duplicate sysfs directories and files
Date: Wed, 8 Mar 2006 17:03:42 -0800 [thread overview]
Message-ID: <20060309010342.GA13910@kroah.com> (raw)
In-Reply-To: <20060308010205.7e989a5a.akpm@osdl.org>
On Wed, Mar 08, 2006 at 01:02:05AM -0800, Andrew Morton wrote:
> Greg KH <greg@kroah.com> wrote:
> >
> > Hi,
> >
> > I spent some time tonight trying to track down how to fix the issue of
> > duplicate sysfs files and/or directories. This happens when you try to
> > create a kobject with the same name in the same directory. The creation
> > of the second kobject will fail, but the directory will remain in sysfs.
> >
> > Now I know this isn't a normal operation, but it would be good to fix
> > this eventually. I traced the issue down to fs/sysfs/dir.c:create_dir()
> > and the check for:
> > if (error && (error != -EEXIST)) {
> >
> > Problem is, error is set to -EEXIST, so we don't clean up properly. Now
> > I know we can't just not check for this, as if you do that error
> > cleanup, the original kobject's sysfs entry gets very messed up (ls -l
> > does not like it at all...)
> >
> > But I can't seem to figure out what exactly we need to do to clean up
> > properly here.
> >
> > Do you, or anyone else, have any pointers or ideas?
> >
>
> Emit a loud warning and don't bother cleaning up - leave the current
> behaviour as-is. Whatever takes the least amount code and has the minimum
> end-user impact, IMO.
Yeah, we do give a warning. Well, we used to always do it, but now that
more people are not using kobject_register() but only kobject_add(), it
doesn't always show up...
Here's a patch that I've added to my queue that fixes the warn issue,
but it still would be nice to fix up sysfs someday.
thanks,
greg k-h
---
lib/kobject.c | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
--- gregkh-2.6.orig/lib/kobject.c
+++ gregkh-2.6/lib/kobject.c
@@ -194,6 +194,17 @@ int kobject_add(struct kobject * kobj)
unlink(kobj);
if (parent)
kobject_put(parent);
+
+ /* be noisy on error issues */
+ if (error == -EEXIST)
+ printk("kobject_add failed for %s with -EEXIST, "
+ "don't try to register things with the "
+ "same name in the same directory.\n",
+ kobject_name(kobj));
+ else
+ printk("kobject_add failed for %s (%d)\n",
+ kobject_name(kobj), error);
+ dump_stack();
}
return error;
@@ -207,18 +218,13 @@ int kobject_add(struct kobject * kobj)
int kobject_register(struct kobject * kobj)
{
- int error = 0;
+ int error = -EINVAL;
if (kobj) {
kobject_init(kobj);
error = kobject_add(kobj);
- if (error) {
- printk("kobject_register failed for %s (%d)\n",
- kobject_name(kobj),error);
- dump_stack();
- } else
+ if (!error)
kobject_uevent(kobj, KOBJ_ADD);
- } else
- error = -EINVAL;
+ }
return error;
}
next prev parent reply other threads:[~2006-03-09 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 7:53 problem with duplicate sysfs directories and files Greg KH
2006-03-08 9:02 ` Andrew Morton
2006-03-09 1:03 ` Greg KH [this message]
2006-03-09 2:58 ` Maneesh Soni
2006-03-09 5:58 ` Greg KH
2006-03-09 14:10 ` Maneesh Soni
2006-03-10 0:13 ` Greg KH
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=20060309010342.GA13910@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=mochel@digitalimplant.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.