From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev segfaults with bad permissions file
Date: Tue, 14 Sep 2004 16:50:57 +0000 [thread overview]
Message-ID: <20040914165057.GA29009@kroah.com> (raw)
In-Reply-To: <200409141453.12856.>
On Tue, Sep 14, 2004 at 04:13:25PM +0200, Kay Sievers wrote:
> On Tue, Sep 14, 2004 at 02:53:12PM +0200, Loleslaw wrote:
> > 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.
>
> Yeah, thanks for pointing that out. It only happens if the file ends with
> whitespace-only lines. Here is a fix and a test for udev-test.pl to
> cover that case.
Applied, thanks.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
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:[~2004-09-14 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 12:53 udev segfaults with bad permissions file Loleslaw
2004-09-14 14:13 ` Kay Sievers
2004-09-14 16:50 ` 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=20040914165057.GA29009@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).