Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [PATCH] fix build error of marker.c
Date: Tue, 28 Oct 2008 01:44:53 -0400	[thread overview]
Message-ID: <20081028054453.GA16478@Krystal> (raw)
In-Reply-To: <20081028141551.AAB6.KOSAKI.MOTOHIRO@jp.fujitsu.com>

* KOSAKI Motohiro (kosaki.motohiro at jp.fujitsu.com) wrote:
> Hi Mathieu,
> 
> I got lttng from following tree.
> but it can't build.
> 
> $ git-clone  git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git
> 
> Perhaps, I got code form wrong git repo?
> 

Hi Kosaki,

Ah, it's been a while I've enabled the "userspace markers ABI" option in
my test tree. So yes, I broke it by changing the markers mutexes. I am
releasing LTTng 0.49 at the moment which fixes the problem. Your fix
does not follow the new locking semantics of marker.c, I now use
"lock_modules()" to protect the markers rather than markers_mutex.

And yes, you are using the correct git repository.

Thanks for reporting this issue.

Mathieu

> 
> 
> Patch against: head of the repository of git://git.kernel.org/pub/scm/linux/kernel/git/compudj/linux-2.6-lttng.git
> 
> ------------------------------------------------
> fix following build error.
> 
> 
>   CC      kernel/marker.o
> kernel/marker.c: In function ?sys_marker?:
> kernel/marker.c:993: error: ?markers_mutex? undeclared (first use in this function)
> kernel/marker.c:993: error: (Each undeclared identifier is reported only once
> kernel/marker.c:993: error: for each function it appears in.)
> kernel/marker.c: In function ?marker_update_processes?:
> kernel/marker.c:1081: error: ?markers_mutex? undeclared (first use in this function)
> kernel/marker.c: In function ?marker_update_process?:
> kernel/marker.c:1111: error: ?markers_mutex? undeclared (first use in this function)
> kernel/marker.c: In function ?exit_user_markers?:
> kernel/marker.c:1159: error: ?markers_mutex? undeclared (first use in this function)
> kernel/marker.c: In function ?is_marker_enabled?:
> kernel/marker.c:1175: error: ?markers_mutex? undeclared (first use in this function)
> 
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro at jp.fujitsu.com>
> 
> ---
>  kernel/marker.c |    6 ++++++
>  1 file changed, 6 insertions(+)
> 
> Index: b/kernel/marker.c
> ===================================================================
> --- a/kernel/marker.c	2008-10-28 12:42:14.000000000 +0900
> +++ b/kernel/marker.c	2008-10-28 13:46:49.000000000 +0900
> @@ -36,6 +36,12 @@ extern struct marker __stop___markers[];
>  static const int marker_debug;
>  
>  /*
> + * markers_mutex nests inside module_mutex. Markers mutex protects the builtin
> + * and module markers and the hash table.
> + */
> +static DEFINE_MUTEX(markers_mutex);
> +
> +/*
>   * Marker hash table, containing the active markers.
>   * lock_modules() protects the builtin and module markers and the hash table.
>   */
> 
> 
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




  reply	other threads:[~2008-10-28  5:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28  5:21 KOSAKI Motohiro
2008-10-28  5:44 ` Mathieu Desnoyers [this message]
2008-10-28  6:08   ` KOSAKI Motohiro

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=20081028054453.GA16478@Krystal \
    --to=compudj@krystal.dyndns.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox