AFAICT sysfs itself sort of has this problem in 2.5.66 -- it tries
to register itself as a filesystem before the set 'fs' is registered.
It retries later and succeeds but I could never figure out if that was
by design or accident. 8)
This patch helps find some of these problems but I don't think it will
help in this case:
diff -ur --exclude-from=/home/me/exclude linux-2.5.66-ref/lib/kobject.c linux-2.5.66-uni/lib/kobject.c
--- linux-2.5.66-ref/lib/kobject.c Tue Mar 4 22:29:36 2003
+++ linux-2.5.66-uni/lib/kobject.c Sat Mar 29 20:43:26 2003
@ -57,10 +57,15 @
sysfs_remove_dir(kobj);
}
}
+ if (error) {
+ printk("Badness name:%s, err:%d, set:%s\n",
+ kobj->name, error,
+ kobj->kset ? kobj->kset->kobj.name : "<NULL>");
+ WARN_ON(1);
+ }
return error;
}
-
static inline struct kobject * to_kobj(struct list_head * entry)
{
return container_of(entry,struct kobject,entry);
@ -149,7 +154,6 @
if (kobj) {
kobject_init(kobj);
error = kobject_add(kobj);
- WARN_ON(error);
} else
error = -EINVAL;
return error;
-- Chuck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/