* BUG? possible race between tasklet_action and tasklet_kill
@ 2009-09-11 17:00 Chris Friesen
0 siblings, 0 replies; only message in thread
From: Chris Friesen @ 2009-09-11 17:00 UTC (permalink / raw)
To: Linux kernel
I think I may have discovered a race between tasklet_action and
tasklet_kill. Given how long this code has been around, I assume that
I'm simply not understanding the purposes of tasklet_kill correctly, but
it seems like there's a mechanism whereby we could hit the BUG path in
tasklet_action().
cpu A cpu B
starts tasklet_kill()
does while loop until
TASKLET_STATE_SCHED not set
runs tasklet_schedule()
starts tasklet_action()
tasklet_unlock_wait()
if (tasklet_trylock(t)) {
clear_bit(TASKLET_STATE_SCHED)
test_and_clear_bit(TASKLET_STATE_SCHED
BUG
Is this a valid issue, or is this an improper usage pattern somehow?
Thanks,
Chris
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-09-11 17:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-11 17:00 BUG? possible race between tasklet_action and tasklet_kill Chris Friesen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox