lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 1 Jun 2009 11:06:38 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Steven Whitehouse <swhiteho@...hat.com>
cc:	linux-kernel@...r.kernel.org, cluster-devel@...hat.com
Subject: Re: trace: Add exports to use __print_symbolic and __print_flags
 from a module


On Mon, 1 Jun 2009, Steven Whitehouse wrote:

> 
> A patch to allow the use of __print_symbolic and __print_flags
> from a module. This allows the current GFS2 tracing patch to
> build. This is against the latest -tip tree.
> 
> Signed-off-by: Steven Whitehouse <swhiteho@...hat.com>

Thanks! I'll apply it.

-- Steve

> 
> diff --git a/kernel/trace/trace_output.c b/kernel/trace/trace_output.c
> index c12d95d..0fe3b22 100644
> --- a/kernel/trace/trace_output.c
> +++ b/kernel/trace/trace_output.c
> @@ -17,6 +17,7 @@
>  static DECLARE_RWSEM(trace_event_mutex);
>  
>  DEFINE_PER_CPU(struct trace_seq, ftrace_event_seq);
> +EXPORT_PER_CPU_SYMBOL(ftrace_event_seq);
>  
>  static struct hlist_head event_hash[EVENT_HASHSIZE] __read_mostly;
>  
> @@ -250,6 +251,7 @@ ftrace_print_flags_seq(struct trace_seq *p, const char *delim,
>  
>  	return p->buffer;
>  }
> +EXPORT_SYMBOL(ftrace_print_flags_seq);
>  
>  const char *
>  ftrace_print_symbols_seq(struct trace_seq *p, unsigned long val,
> @@ -275,6 +277,7 @@ ftrace_print_symbols_seq(struct trace_seq *p, unsigned long val,
>  
>  	return p->buffer;
>  }
> +EXPORT_SYMBOL(ftrace_print_symbols_seq);
>  
>  #ifdef CONFIG_KRETPROBES
>  static inline const char *kretprobed(const char *name)
> 
> 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists