From: "John L. Fjellstad" <john-hotplug@fjellstad.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] symlink name and possible overflow in create_node()
Date: Wed, 18 Feb 2004 08:27:20 +0000 [thread overview]
Message-ID: <20040218082719.GA3111@fjellstad.org> (raw)
In-Reply-To: <20040217190010.GA9773@suse.de>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On Tue, Feb 17, 2004 at 08:47:04PM +0100, Kay Sievers wrote:
> Oh, we have strfieldcpy() for this.
> Maybe we should have strfieldcat() too.
>
> Anyone, who wants to send a patch? :)
Andrey Borzenkov has that function in his include multiple
udev.rules patch.
--
John
email: john@fjellstad.org Quis custodiet ipsos custodes
Yahoo Messenger: jfjellstad
MSN Messenger: liemfjellstad@hotmail.com
web: http://www.fjellstad.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2004-02-18 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 19:00 [PATCH] symlink name and possible overflow in create_node() Olaf Hering
2004-02-17 19:22 ` Johannes Erdfelt
2004-02-17 19:47 ` Kay Sievers
2004-02-18 8:27 ` John L. Fjellstad [this message]
2004-02-18 10:08 ` Kay Sievers
2004-02-18 11:03 ` John L. Fjellstad
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=20040218082719.GA3111@fjellstad.org \
--to=john-hotplug@fjellstad.org \
--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.