Hi :) On Wed, May 2, 2012 at 8:43 PM, Panagiotis Sakkos <panos.sakkos@xxxxxxx> wrote: > Hi, > > I am trying to log information from within the kernel with the use of a unix > socket (/dev/log). > My code is a kprobe handler, so while executing I am atomic and > uninterrupted. > The crashes begin when I do stress tests against my module, so i.e. more > than 50 logs per second. > Maybe that's the problem......under "rapid" call, kprobe handler must allocate stack for unwinding the call more and more. Not to mention that it began to push reentrancy problem to the surface. Regarding reentrancy, IMO think like this...your handler called once...ok fine, twice, perhaps still fine...but maybe more than 50 per sec, not to mention the possibility that they are executed by more than 1 core at once, perhaps that's the problem. race condition.... -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
