From: Sebastian Krahmer <krahmer-l3A5Bk7waGM@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cifskey: better use snprintf()
Date: Wed, 9 Apr 2014 08:11:04 +0200 [thread overview]
Message-ID: <20140409061104.GA27130@suse.de> (raw)
In-Reply-To: <20140408132326.7bb0de89-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On Tue, Apr 08, 2014 at 01:23:26PM -0400, Jeff Layton wrote:
> > > If you do that then you don't need to use strlen() either.
> > >
> > > --
> > > Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
> >
>
> Ok, I think you're correct about snprintf. I got it confused with
> sprintf, which doesn't always NULL-terminate.
>
> If it does indeed always null-terminate then there is indeed no harm in
> using strlen, it's just not as efficient. Why not instead simply take
> the return value of snprintf and use that to determine whether the
> output got truncated? I think we'd rather return an error if it is,
> than pass in a possibly bogus string to add_key().
Could be done indeed.
Sebastian
--
~ perl self.pl
~ $_='print"\$_=\47$_\47;eval"';eval
~ krahmer-l3A5Bk7waGM@public.gmane.org - SuSE Security Team
next prev parent reply other threads:[~2014-04-09 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 12:44 [PATCH] cifskey: better use snprintf() Sebastian Krahmer
[not found] ` <20140408124444.GB23274-l3A5Bk7waGM@public.gmane.org>
2014-04-08 14:32 ` Jeff Layton
[not found] ` <20140408103212.356655ac-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-04-08 14:41 ` Sebastian Krahmer
[not found] ` <20140408144129.GA7863-l3A5Bk7waGM@public.gmane.org>
2014-04-08 17:23 ` Jeff Layton
[not found] ` <20140408132326.7bb0de89-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2014-04-09 6:11 ` Sebastian Krahmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-14 9:39 Sebastian Krahmer
[not found] ` <20140414093941.GA7017-l3A5Bk7waGM@public.gmane.org>
2014-04-14 17:00 ` Jeff Layton
2014-04-16 12:14 ` Jeff Layton
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=20140409061104.GA27130@suse.de \
--to=krahmer-l3a5bk7wagm@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.