Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] Bug in add_marker (marker.c)
Date: Mon, 02 Aug 2010 23:14:36 -0400	[thread overview]
Message-ID: <4C57899C.7050106@polymtl.ca> (raw)
In-Reply-To: <20100802194854.GC3910@Krystal>

Applied to ust. Thanks.

pmf

On 08/02/2010 03:48 PM, Mathieu Desnoyers wrote:
> Good catch ! Here is the patch.
>
> Pierre-Marc, can you apply it to UST too ?
>
> Thanks,
>
> Mathieu
>
> markers fix out of bound array
>
> While creating my own probes, I've observed that I get format mismatch error...
> While digging into the executed code I observe that my format (stored in a
> marker_entry) was overwritten by a new allocated structure. Finally I found
> that in add_marker function the format pointer seems to be set to the wrong
> position:
>
> e->format =&e->name[channel_len + name_len];
> while the proper assignment should be
> e->format =&e->name[name_len];
>
> indead:
>
> size_t channel_len = strlen(channel) + 1;
> size_t name_len = strlen(name) + 1;
> ...
> size_t format_len ...= strlen(format) + 1;
>
> and
>
> struct marker_entry {
> ....
>      char channel[0];        /* Contains channel'\0'name'\0'format'\0' *     /
>
> };
>
> ...
>
> e = kmalloc(sizeof(struct marker_entry)
>        + channel_len + name_len + format_len,
>        GFP_KERNEL);
> ....
> e->name =&e->channel[channel_len];
>
> Rgds,
> Damien COTTIER.
>
> Signed-off-by: Mathieu Desnoyers<mathieu.desnoyers at efficios.com>
> ---
>   kernel/marker.c |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6-lttng/kernel/marker.c
> ===================================================================
> --- linux-2.6-lttng.orig/kernel/marker.c	2010-08-02 15:44:51.000000000 -0400
> +++ linux-2.6-lttng/kernel/marker.c	2010-08-02 15:45:55.000000000 -0400
> @@ -436,7 +436,7 @@ static struct marker_entry *add_marker(c
>   	e->name =&e->channel[channel_len];
>   	memcpy(e->name, name, name_len);
>   	if (format) {
> -		e->format =&e->name[channel_len + name_len];
> +		e->format =&e->name[name_len];
>   		memcpy(e->format, format, format_len);
>   		if (strcmp(e->format, MARK_NOARGS) == 0)
>   			e->call = marker_probe_cb_noarg;





      reply	other threads:[~2010-08-03  3:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2AC7D4AD8BA1C640B4C60C61C8E5201539DED6C058@EXDCVYMBSTM006.EQ1STM.local>
2010-08-02 19:48 ` Mathieu Desnoyers
2010-08-03  3:14   ` Pierre-Marc Fournier [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=4C57899C.7050106@polymtl.ca \
    --to=pierre-marc.fournier@polymtl.ca \
    /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