[PATCH (resend) 0/2] workqueue lockup debugging

I recently experienced a lockup in the wireless code due to the
scenario described in patch 1 and wanted to have lockdep warn
about such scenarios as a way to catch such bugs in other
subsystems as well as to make sure we wouldn't get such things
ever again.

In discussions with Oleg and Ingo it turned out that there's
another possible deadlock with the now-recommended API of
cancel_work_sync() and I also found a way to make lockdep
catch that; it is addressed by patch 2.

Ingo thinks this could also have caught a similar lockup in the
DVB subsystem and would like to see it in .23.

johannes

-
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:
  • [PATCH (resend) 1/2] workqueue: debug flushing deadlocks with lockdep
    • From: Johannes Berg <[email protected]>
  • [PATCH (resend) 2/2] workqueue: debug work related deadlocks with lockdep
    • From: Johannes Berg <[email protected]>

• Prev by Date: [PATCH] Fix leak on /proc/lockdep_stats
• Next by Date: [PATCH (resend) 2/2] workqueue: debug work related deadlocks with lockdep
• Previous by thread: [PATCH] AFS: Fix file locking
• Next by thread: [PATCH (resend) 2/2] workqueue: debug work related deadlocks with lockdep
• 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]