linux-kernel - Re: 2.6.23-rc2-mm1: rcutorture xtime usage

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070811193937.GB13410@linux.vnet.ibm.com>
Date:	Sat, 11 Aug 2007 12:39:37 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>, Josh Triplett <josh@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc2-mm1: rcutorture xtime usage

On Sat, Aug 11, 2007 at 08:09:09PM +0200, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
> 
> > Add an EXPORT_SYMBOL_GPL() for cpu_clock() and make rcutorture.c use it.
> > Compiles, but not yet tested.
> > 
> > Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> 
> > --- linux-2.6.23-rc2/kernel/sched.c	2007-08-03 19:49:55.000000000 -0700
> > +++ linux-2.6.23-rc2-rcutorturesched/kernel/sched.c	2007-08-10 17:22:57.000000000 -0700
> > @@ -394,6 +394,8 @@ unsigned long long cpu_clock(int cpu)
> >  	return now;
> >  }
> >  
> > +EXPORT_SYMBOL_GPL(cpu_clock);
> 
> sure enough,
> 
> Acked-by: Ingo Molnar <mingo@...e.hu>

Thank you!

Just for the record, given that the xtime API that it replaces
was EXPORT_SYMBOL(), I would have not objection to this also being
EXPORT_SYMBOL().  That said, I know of no specific reason for it being
other than EXPORT_SYMBOL_GPL().

						Thanx, Paul
-
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/