From: Loleslaw <lollul@wp.pl>
To: linux-hotplug@vger.kernel.org
Subject: udev segfaults with bad permissions file
Date: Tue, 14 Sep 2004 12:53:12 +0000 [thread overview]
Message-ID: <200409141453.12856.> (raw)
Hi,
Since I started using udev-031 on my gentoo udevstart would just segfault
(udev-030 worked). As it turned out I had a file in /etc/udev/permissions.d
with a single space in one line. I've cleaned the file and it works all
right, but I thought you could be interested.
I've traced it to function namedev_init_permissions in namedev_parse.c
I don't know C well enough to suggest a patch.
Regards,
Marek
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
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
next reply other threads:[~2004-09-14 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 12:53 Loleslaw [this message]
2004-09-14 14:13 ` udev segfaults with bad permissions file Kay Sievers
2004-09-14 16:50 ` 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=200409141453.12856. \
--to=lollul@wp.pl \
--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).