linux-kernel - Re: [PATCH] percpu-refcount: Export symbols

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:	Sun, 13 Oct 2013 04:09:25 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Matias Bjorling <m@...rling.me>
Cc:	tj@...nel.org, koverstreet@...gle.com, tytso@....edu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] percpu-refcount: Export symbols

On Fri, Oct 11, 2013 at 02:28:12PM +0200, Matias Bjorling wrote:
> Need to be exported for being used within modules.
> 
> Signed-off-by: Matias Bjorling <m@...rling.me>

I will bite...  Why not EXPORT_SYMBOL_GPL()?

							Thanx, Paul

> ---
>  lib/percpu-refcount.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/lib/percpu-refcount.c b/lib/percpu-refcount.c
> index 7deeb62..25b9ac7 100644
> --- a/lib/percpu-refcount.c
> +++ b/lib/percpu-refcount.c
> @@ -53,6 +53,7 @@ int percpu_ref_init(struct percpu_ref *ref, percpu_ref_func_t *release)
>  	ref->release = release;
>  	return 0;
>  }
> +EXPORT_SYMBOL(percpu_ref_init);
> 
>  /**
>   * percpu_ref_cancel_init - cancel percpu_ref_init()
> @@ -84,6 +85,7 @@ void percpu_ref_cancel_init(struct percpu_ref *ref)
>  		free_percpu(ref->pcpu_count);
>  	}
>  }
> +EXPORT_SYMBOL(percpu_ref_cancel_init);
> 
>  static void percpu_ref_kill_rcu(struct rcu_head *rcu)
>  {
> @@ -156,3 +158,4 @@ void percpu_ref_kill_and_confirm(struct percpu_ref *ref,
> 
>  	call_rcu_sched(&ref->rcu, percpu_ref_kill_rcu);
>  }
> +EXPORT_SYMBOL(percpu_ref_kill_and_confirm);
> -- 
> 1.8.1.2
> 

--
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/