All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bellman <bellman@nsc.liu.se>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: Lars Wirzenius <liw@liw.fi>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs use safe string manipulation functions
Date: Thu, 10 Feb 2011 13:41:06 +0100	[thread overview]
Message-ID: <4D53DCE2.50306@nsc.liu.se> (raw)
In-Reply-To: <AANLkTi=gBD0F143APDJEYSw+LXkrS+aOeq6zR-o8MFzs@mail.gmail.com>

On 2011-02-10 13:27, Olaf van der Spek wrote:

> On Thu, Feb 10, 2011 at 12:54 PM, Lars Wirzenius <liw@liw.fi> wrote:

>> snprintf is standard, and should be about as safe as it gets with the
>> glibc functions.
> 
> But snprintf is not like strlcpy.

It is indeed uglier to write 'snprintf(dst, size, "%s", src)' instead of
'strlcpy(dst, src, size)', but both the effect and the return value should
be identical.

	/Bellman

  reply	other threads:[~2011-02-10 12:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 12:22 [PATCH] Btrfs-progs use safe string manipulation functions Eduardo Silva
2011-02-07 18:17 ` Goffredo Baroncelli
2011-02-10 11:08 ` Thomas Bellman
2011-02-10 11:21   ` Olaf van der Spek
2011-02-10 11:37     ` Jeremy Sanders
2011-02-10 11:39       ` Olaf van der Spek
2011-02-10 13:29         ` Eduardo Silva
2011-02-10 13:34           ` Olaf van der Spek
2011-02-10 13:41             ` Eduardo Silva
     [not found]             ` <1297345079.28159.14.camel@monotop>
2011-02-10 13:52               ` Olaf van der Spek
2011-02-10 14:00                 ` Eduardo Silva
2011-02-10 14:05                   ` Olaf van der Spek
2011-02-10 18:39           ` Goffredo Baroncelli
2011-02-11 12:41           ` Lars Wirzenius
2011-02-10 11:54       ` Lars Wirzenius
2011-02-10 12:27         ` Olaf van der Spek
2011-02-10 12:41           ` Thomas Bellman [this message]
2011-02-10 15:17       ` Olaf van der Spek
2011-02-10 11:49   ` Eduardo Silva

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=4D53DCE2.50306@nsc.liu.se \
    --to=bellman@nsc.liu.se \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=liw@liw.fi \
    --cc=olafvdspek@gmail.com \
    /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.