From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c
Date: Fri, 23 Apr 2004 08:02:40 -0500 [thread overview]
Message-ID: <200404230802.42293.dtor_core@ameritech.net> (raw)
In-Reply-To: <1082723147.1843.14.camel@merlin>
On Friday 23 April 2004 07:25 am, Marcel Holtmann wrote:
> Hi Dmitry,
>
> > The latest change in sysfs/symlink (conversion to use kobject_name instead
> > of name fiedld directly) broke atmel_cs driver:
> >
> > Apr 23 00:30:10 core kernel: Oops: 0000 [#1]
> > Apr 23 00:30:10 core kernel: PREEMPT
> > Apr 23 00:30:10 core kernel: CPU: 0
> > Apr 23 00:30:10 core kernel: EIP: 0060:[<c0182ef9>] Not tainted
> > Apr 23 00:30:10 core kernel: EFLAGS: 00010246 (2.6.6-rc2)
> > Apr 23 00:30:10 core kernel: EIP is at object_path_length+0x19/0x30
<skip>
> > Apr 23 00:30:10 core kernel: Call Trace:
> > Apr 23 00:30:10 core kernel: [<c0182f99>] sysfs_create_link+0x29/0x140
> > Apr 23 00:30:10 core kernel: [<c01ac578>] kobject_hotplug+0x58/0x60
> > Apr 23 00:30:10 core kernel: [<c0211490>] class_device_dev_link+0x30/0x40
<skip>
> >
> > Below is the "fix" that helps avoid oopsing, and should be removed when
> > atmel_cs driver properly registers atmel_device.
>
> I haven't tested it yet, but the same problem should apply to the
> bt3c_cs driver for the 3Com Bluetooth card. Are there any patches
> available that integrates the PCMCIA subsystem into the driver model, so
> we don't have to hack around it if a firmware download is needed?
>
I do not know. But the problem seems to be somewhat widespread - I just got
oops with the following trace:
[<c0182f99>] sysfs_create_link+0x29/0x140
[<c01ac578>] kobject_hotplug+0x58/0x60
[<c0211490>] class_device_dev_link+0x30/0x40
[<c02117ad>] class_device_add+0xed/0x130
[<e185ffab>] usb_register_dev+0x12b/0x170 [usbcore]
[<e1b2bf2a>] hiddev_connect+0x7a/0x120 [usbhid]
I think we should not oops, just complain loudly, when we come across a
kobject which has never beek kobject_add()ed, like in patch below.
--
Dmitry
===== include/linux/kobject.h 1.26 vs edited =====
--- 1.26/include/linux/kobject.h Thu Mar 11 08:20:22 2004
+++ edited/include/linux/kobject.h Fri Apr 23 07:58:52 2004
@@ -39,6 +39,11 @@
static inline char * kobject_name(struct kobject * kobj)
{
+ if (unlikely(!kobj->k_name)) {
+ printk("kobject_name(): not registered kobject\n");
+ dump_stack();
+ return kobj->name;
+ }
return kobj->k_name;
}
next prev parent reply other threads:[~2004-04-23 13:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 6:42 [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c Dmitry Torokhov
2004-04-23 12:25 ` Marcel Holtmann
2004-04-23 13:02 ` Dmitry Torokhov [this message]
2004-04-23 14:26 ` Marcel Holtmann
2004-04-23 16:55 ` Dmitry Torokhov
2004-04-23 17:16 ` Greg KH
2004-04-23 18:50 ` Marcel Holtmann
2004-04-23 19:46 ` Greg KH
2004-04-23 20:35 ` Russell King
2004-04-23 21:02 ` Marcel Holtmann
2004-04-23 15:31 ` Greg KH
2004-04-23 17:19 ` Greg KH
2004-04-23 18:03 ` Greg KH
2004-04-24 6:44 ` Dmitry Torokhov
2004-04-25 2:49 ` Greg KH
2004-04-25 21:48 ` Dmitry Torokhov
2004-05-04 21:04 ` Greg KH
2004-05-05 7:08 ` Dmitry Torokhov
2004-05-07 23:25 ` Greg KH
2004-04-26 10:19 ` Vojtech Pavlik
2004-04-23 19:55 ` Russell King
2004-04-23 20:14 ` Marcel Holtmann
2004-04-23 20:39 ` Russell King
2004-04-25 21:53 ` Dmitry Torokhov
2004-04-25 22:58 ` Russell King
2004-04-26 10:35 ` Marcel Holtmann
2004-04-26 12:32 ` Dmitry Torokhov
2004-04-26 13:09 ` Marcel Holtmann
2004-04-27 5:57 ` Dmitry Torokhov
2004-04-26 12:26 ` Dmitry Torokhov
2004-04-23 15:28 ` 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=200404230802.42293.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=simon@thekelleys.org.uk \
/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