All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	namhyung@kernel.org, acme@kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 8/8] tools, perf: Add asprintf replacement
Date: Mon, 20 Oct 2014 21:21:48 +0200	[thread overview]
Message-ID: <20141020192148.GF9913@krava.brq.redhat.com> (raw)
In-Reply-To: <CAMuHMdUdSK=ibgLowJcsduWykcfS7JacHO8wOcYb0hMLtKCwpQ@mail.gmail.com>

On Mon, Oct 20, 2014 at 09:13:58PM +0200, Geert Uytterhoeven wrote:
> On Mon, Oct 20, 2014 at 8:28 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> >> +int vasprintf(char **str, const char *fmt, va_list ap)
> >> +{
> >> +     char buf[1024];
> >
> > could you please make it work for generic buf len?
> 
> The actual size above doesn't matter, except for stack usage.
> It could be 1 (are there any bugs triggered when using zero? ;-).
> The real buffer is allocated by malloc() below.
> 
> >> +     int len = vsnprintf(buf, sizeof buf, fmt, ap);

hum, really? the message is formated in here ^^^
into buffer on stack 'buf[1024]'

> >
> > WARNING: sizeof buf should be sizeof(buf)
> >
> >> +
> >> +     *str = malloc(len + 1);
> >> +     if (!*str)
> >> +             return -1;
> >> +     strcpy(*str, buf);

and copied into allocated buffer in here

the buf size 1024 limits the maximum formated string length to 1024,
which is probably not crossed by current perf usage.. but still making
it generic is not that hard

jirka

> >> +     return len;
> >> +}
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds

  reply	other threads:[~2014-10-20 19:22 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 23:37 Implement lbr-as-callgraph v10 Andi Kleen
2014-09-26 23:37 ` [PATCH 1/8] perf, tools: Support handling complete branch stacks as histograms Andi Kleen
2014-10-20  7:54   ` Jiri Olsa
2014-10-20 10:10   ` Jiri Olsa
2014-10-22  1:03   ` Namhyung Kim
2014-11-11 23:31     ` Andi Kleen
2014-11-17  6:23       ` Namhyung Kim
2014-11-18  2:08         ` Andi Kleen
2014-09-26 23:37 ` [PATCH 2/8] perf, tools: Add --branch-history option to report Andi Kleen
2014-10-20  7:54   ` Jiri Olsa
2014-10-20 17:51   ` Jiri Olsa
2014-10-22  1:26   ` Namhyung Kim
2014-11-12  0:05     ` Andi Kleen
2014-11-17  6:31       ` Namhyung Kim
2014-11-18  2:01         ` Andi Kleen
2014-09-26 23:37 ` [PATCH 3/8] perf, tools: Enable printing the srcline in the history Andi Kleen
2014-10-20 17:57   ` Jiri Olsa
2014-09-26 23:37 ` [PATCH 4/8] perf, tools: Only print base source file for srcline Andi Kleen
2014-09-26 23:37 ` [PATCH 5/8] perf, tools: Support source line numbers in annotate Andi Kleen
2014-10-20 18:06   ` Jiri Olsa
2014-10-20 18:17     ` Jiri Olsa
2014-11-12  0:36     ` Andi Kleen
2014-09-26 23:37 ` [PATCH 6/8] tools, perf: Make get_srcline fall back to sym+offset Andi Kleen
2014-09-26 23:37 ` [PATCH 7/8] tools, perf: Make srcline output address with -v Andi Kleen
2014-10-20 18:20   ` Jiri Olsa
2014-09-26 23:37 ` [PATCH 8/8] tools, perf: Add asprintf replacement Andi Kleen
2014-10-20 18:28   ` Jiri Olsa
2014-10-20 19:13     ` Geert Uytterhoeven
2014-10-20 19:21       ` Jiri Olsa [this message]
2014-10-20 19:33         ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2014-09-15 23:54 Implement lbr-as-callgraph v9 Andi Kleen
2014-09-15 23:54 ` [PATCH 8/8] tools, perf: Add asprintf replacement Andi Kleen

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=20141020192148.GF9913@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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.