Debugging race conditions?

[archieval briones]

I am a kernel newbie also but I can recommend taking note of the scheduling policy that you used in creating your threads. If possible add some delay in some threads to see if they will be preempted by the others or not. Examine if the priorities of the threads are the same, static and dynamic priority. And also take note of the code sections that might sleep. If you are coding interrupt handlers, use spin locks in the interrupt handlers and codes running in task context.

I hope I helped a bit >_<

Registered Linux User #478208

--- On Tue, 5/26/09, pradeep singh <pradeep.rautela at gmail.com> wrote:

From: pradeep singh <pradeep.rautela at gmail.com>
Subject: Debugging race conditions?
To: "kernelnewbie" <kernelnewbies at nl.linux.org>
Cc: "kernelmentors" <kernel-mentors at selenic.com>
Date: Tuesday, May 26, 2009, 4:57 PM

Hi All,

I am having a tough time debugging concurrency issues it seems.
I find myself flabbergasted at debugging panic because of race issues.

I would like to ask people here, if they have any advice on how to
properly approach these specific set of panics?
How do they do it?
Are there any rules of thumbs which can help me?

Thanks in Advance
          --Pradeep
-- 
Pradeep
_______________________________________________
Kernel-mentors mailing list
Kernel-mentors at selenic.com
http://selenic.com/mailman/listinfo/kernel-mentors



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/kernel-mentors/attachments/20090526/046ffbc5/attachment.htm