2012/8/14 Ezequiel Garcia <elezegar...@gmail.com> > Hey wanny, > > On Tue, Aug 14, 2012 at 1:04 AM, Mulyadi Santosa > <mulyadi.sant...@gmail.com> wrote: > > Hi.. :) > > > > On Tue, Aug 14, 2012 at 9:14 AM, 王哲 <wangzhe5...@gmail.com> wrote: > >> i use the __init for function print_k. > >> in my opinion after the fisrt invoking the print_k in the hello_init. > >> the memory of print_k will be freed,and the second invoking will > >> not be executed.but the result of second invoking is executing . > >> > >> why? > > > > because you're still in module_init.... :) > > > > > > Yes, and the function is still in the stack! > > On the other hand.. think what would happen if things would work > like you say. > > We would have a *very* strange behavior, > and pretty counter-intuitive, don't you think so? >
Thank you very much for reply. as you say,and function is still in the stack,don't be freed in the memory,what is __init had done? who can give a sample example to explain the difference existing __init or not?
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
