Re: [PATCH] rcutorture: don't mark torture_init_{begin,end} with __init

2014-04-29 Thread Will Deacon
On Mon, Apr 28, 2014 at 09:13:04PM +0100, Paul E. McKenney wrote: > On Mon, Apr 28, 2014 at 08:03:35PM +0100, Will Deacon wrote: > > By the time rcutorture is initialised via its module_init callback, the > > .init.text section of torture.ko has already been freed, so the calls to > > torture_init{

Re: [PATCH] rcutorture: don't mark torture_init_{begin,end} with __init

2014-04-28 Thread Paul E. McKenney
On Mon, Apr 28, 2014 at 08:03:35PM +0100, Will Deacon wrote: > By the time rcutorture is initialised via its module_init callback, the > .init.text section of torture.ko has already been freed, so the calls to > torture_init{begin,end} end up branching to junk. > > This patch removes the __init an

[PATCH] rcutorture: don't mark torture_init_{begin,end} with __init

2014-04-28 Thread Will Deacon
By the time rcutorture is initialised via its module_init callback, the .init.text section of torture.ko has already been freed, so the calls to torture_init{begin,end} end up branching to junk. This patch removes the __init annotations from torture_init_{begin,end} to make sure the code is there