Re: [PATCH -rt] Fix TASKLET_STATE_SCHED WARN_ON()

* john stultz <[email protected]> wrote:

> This fix avoids this race by making sure *after* we've locked the 
> tasklet that the STATE_SCHED bit is set before adding it to the list.
> 
> Does it look ok to you?

ah - nice!! What would be the worst-case effect of this bug? (besides 
the WARN_ON()?) In any case, this fix will be in -rt10. Great work!

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH -rt] Fix TASKLET_STATE_SCHED WARN_ON()
    • From: john stultz <[email protected]>

• References:
  • [PATCH -rt] Fix TASKLET_STATE_SCHED WARN_ON()
    • From: john stultz <[email protected]>

• Prev by Date: Re: [PATCH 4/4] mm: variable length argument support
• Next by Date: Re: [PATCH 4/4] mm: variable length argument support
• Previous by thread: [PATCH -rt] Fix TASKLET_STATE_SCHED WARN_ON()
• Next by thread: Re: [PATCH -rt] Fix TASKLET_STATE_SCHED WARN_ON()
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]