All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] more robust config file parsing in udev/devnaming.c
Date: Wed, 19 Nov 2003 00:23:45 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106920988302174@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106917668928469@msgid-missing>

On Tue, Nov 18, 2003 at 06:29:25PM +0100, Arnd Bergmann wrote:
> After getting a number of different crashes for udev reading broken
> udev.config files, I decided to try to make the parser a little
> more robust.
> 
> The behaviour is changed to stop reading the configuration file
> and logging the broken entry instead of silently ignoring it (is
> that good? It's easy to just print and continue).
> All strcpy()'s to a fixed length string are now implicitly limited
> to the bounds of the target string.
> 
> I kept the -ENODEV return code for now, not sure if there should be
> different ones.

Thanks a lot for this patch, I've applied it.  We should probably
continue on, and not die if we can't read a line of the config file,
that's the nicest way :)

thanks,

greg k-h


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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

      parent reply	other threads:[~2003-11-19  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-18 17:29 [PATCH] more robust config file parsing in udev/devnaming.c Arnd Bergmann
2003-11-19  0:23 ` Greg KH
2003-11-19  0:23 ` 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=marc-linux-hotplug-106920988302174@msgid-missing \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.