Bug#298192: udev: segfault with new rule on startup

Bug#298192: udev: segfault with new rule on startup

[Marco d'Itri]

This rule causes udevstart 054 to segfault:

BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"

----- Forwarded message from Thomas Breitner <debian@tombreit.de> -----

Subject: Bug#298192: udev: segfault with new rule on startup
Reply-To: debian@tombreit.de, 298192@bugs.debian.org
From: Thomas Breitner <debian@tombreit.de>
To: 298192@bugs.debian.org

Thanks, here it is:

mala:~/sourcen/udev-0.054# /etc/init.d/udev restart
Recreating device nodes.../etc/init.d/udev: line 216: 10361 Segmentation fault      udevstart
mala:~/sourcen/udev-0.054# gdb /sbin/udevstart
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /sbin/udevstart

Program received signal SIGSEGV, Segmentation fault.
strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
50              if (s[0] = '\0') {
(gdb) where
#0  strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
#1  0x0804e448 in match_rule (udev=0xbfffdd30, dev=0x805c5d8, class_dev=0x8059168, sysfs_device=0x0) at namedev.c:597
#2  0x0804e52b in namedev_name_device (udev=0xbfffdd30, class_dev=0x8059168) at namedev.c:724
#3  0x0804b262 in udev_add_device (udev=0xbfffdd30, class_dev=0x8059168) at udev_add.c:284
#4  0x0804b97b in add_device (path=0x8059168 "event0", subsystem=0x809eb60 "input") at udev_start.c:112
#5  0x0804bb35 in exec_list (device_list=0xbfffe758) at udev_start.c:155
#6  0x0804be70 in udev_scan_class () at udev_start.c:278
#7  0x0804c034 in udev_start () at udev_start.c:287
#8  0x080499e4 in main (argc=1, argv=0xbffff9b4, envp=0xbffff9bc) at udev.c:149
(gdb)

tschuess,
thomas



Am Montag, den 07.03.2005, 20:18 +0100 schrieb Marco d'Itri:
> On Mar 06, Thomas Breitner <debian@tombreit.de> wrote:
> 
> > Don't know how to enable debugging symbols, can't find it in rules.
> > Please let me know how to enable them...
> Just build the package with "./debian/rules build" and copy
> build-tree/udev-054/udev to /sbin/udev .
> 
> Then run "gdb /sbin/udevstart" and use the commands "run" and "where".
> 
-- 
_____________________________________________
Thomas Breitner

mail@tombreit.de   |   http://www.tombreit.de


----- End forwarded message -----

-- 
ciao,
Marco


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#298192: udev: segfault with new rule on startup

[Kay Sievers]

On Tue, 2005-03-08 at 00:03 +0100, Marco d'Itri wrote:
> This rule causes udevstart 054 to segfault:
> 
> BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"
> 
> ----- Forwarded message from Thomas Breitner <debian@tombreit.de> -----
> 
> Subject: Bug#298192: udev: segfault with new rule on startup
> Reply-To: debian@tombreit.de, 298192@bugs.debian.org
> From: Thomas Breitner <debian@tombreit.de>
> To: 298192@bugs.debian.org
> 
> Thanks, here it is:
> 
> mala:~/sourcen/udev-0.054# /etc/init.d/udev restart
> Recreating device nodes.../etc/init.d/udev: line 216: 10361 Segmentation fault      udevstart
> mala:~/sourcen/udev-0.054# gdb /sbin/udevstart
> GNU gdb 6.3-debian

> Program received signal SIGSEGV, Segmentation fault.
> strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
> 50              if (s[0] = '\0') {
> (gdb) where
> #0  strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50

Yeah, that's a bad bug in the rule matching. The sysfs_device is NULL,
and we try to find the name here. I will fix it.

But I don't know why the sysfs_device is NULL in this case, I can't
reproduce it with the same hardware. Thomas, it would be nice if you can
send the output of:
  udevinfo -a -p /sys/class/net/eth<N>

Thanks,
Kay



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Bug#298192: udev: segfault with new rule on startup

[Greg KH]

On Tue, Mar 08, 2005 at 01:43:58AM +0100, Kay Sievers wrote:
> On Tue, 2005-03-08 at 00:03 +0100, Marco d'Itri wrote:
> > This rule causes udevstart 054 to segfault:
> > 
> > BUS="pci", SUBSYSTEM="net", DRIVER="ipw2100", NAME="wlan"
> > 
> > ----- Forwarded message from Thomas Breitner <debian@tombreit.de> -----
> > 
> > Subject: Bug#298192: udev: segfault with new rule on startup
> > Reply-To: debian@tombreit.de, 298192@bugs.debian.org
> > From: Thomas Breitner <debian@tombreit.de>
> > To: 298192@bugs.debian.org
> > 
> > Thanks, here it is:
> > 
> > mala:~/sourcen/udev-0.054# /etc/init.d/udev restart
> > Recreating device nodes.../etc/init.d/udev: line 216: 10361 Segmentation fault      udevstart
> > mala:~/sourcen/udev-0.054# gdb /sbin/udevstart
> > GNU gdb 6.3-debian
> 
> > Program received signal SIGSEGV, Segmentation fault.
> > strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
> > 50              if (s[0] = '\0') {
> > (gdb) where
> > #0  strcmp_pattern (p=0x805cc60 "ipw2100", s=0x1c4 <Address 0x1c4 out of bounds>) at namedev.c:50
> 
> Yeah, that's a bad bug in the rule matching. The sysfs_device is NULL,
> and we try to find the name here. I will fix it.
> 
> But I don't know why the sysfs_device is NULL in this case, I can't
> reproduce it with the same hardware. Thomas, it would be nice if you can
> send the output of:
>   udevinfo -a -p /sys/class/net/eth<N>

I have heard of this error before, from other users.  I think it depends
on the version of the driver you are using.

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel