From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#298192: udev: segfault with new rule on startup
Date: Tue, 08 Mar 2005 06:53:27 +0000 [thread overview]
Message-ID: <20050308065326.GG17022@kroah.com> (raw)
In-Reply-To: <20050307230305.GA16754@wonderland.linux.it>
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
prev parent reply other threads:[~2005-03-08 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 23:03 Bug#298192: udev: segfault with new rule on startup Marco d'Itri
2005-03-08 0:43 ` Kay Sievers
2005-03-08 6:53 ` Greg KH [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=20050308065326.GG17022@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).