From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev - safer string handling all over the place
Date: Thu, 26 Feb 2004 20:56:00 +0000 [thread overview]
Message-ID: <20040226205600.GB13134@kroah.com> (raw)
In-Reply-To: <20040224225052.GA24733@vrfy.org>
On Wed, Feb 25, 2004 at 12:10:06AM +0100, Kay Sievers wrote:
> On Tue, Feb 24, 2004 at 11:50:52PM +0100, Kay Sievers wrote:
> > Here is the first step towards a safer string handling.
> > More will follow, but for now only the easy ones :)
> >
> > Thanks to all who pointed this out. strncat() isn't a nice function. We
> > all should remember that the destination string is not terminated if the
> > given lenght is shorter than the strlen of the source string.
> >
> > And shame on the various implementers of strfieldcat() I found in the
> > unapplied patches on this list, it's not really better than strncpy()
> > and hides the real problem.
>
> Hmm, bk didn't checked in one file, maybe I edited it again as root.
> Nevermind, here is the more complete version.
Applied, thanks.
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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:[~2004-02-26 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 22:50 [PATCH] udev - safer string handling all over the place Kay Sievers
2004-02-24 23:10 ` Kay Sievers
2004-02-26 20:56 ` 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=20040226205600.GB13134@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).