Olaf Faaland 326172d854 Subclass tq_lock to eliminate a lockdep warning ... When taskq_dispatch() calls taskq_thread_spawn() to create a new thread for a taskq, linux lockdep warns of possible recursive locking. This is a false positive. One such call chain is as follows, when a taskq needs more threads: taskq_dispatch->taskq_thread_spawn->taskq_dispatch The initial taskq_dispatch() holds tq_lock on the taskq that needed more worker threads. The later call into taskq_dispatch() takes dynamic_taskq->tq_lock. Without subclassing, lockdep believes these could potentially be the same lock and complains. A similar case occurs when taskq_dispatch() then calls task_alloc(). This patch uses spin_lock_irqsave_nested() when taking tq_lock, with one of two new lock subclasses: subclass taskq TQ_LOCK_DYNAMIC dynamic_taskq TQ_LOCK_GENERAL any other Signed-off-by: Olaf Faaland <faaland1@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue #480		2015-12-11 16:19:56 -08:00
..
spl	Subclass tq_lock to eliminate a lockdep warning	2015-12-11 16:19:56 -08:00
splat	Limit maximum object size in kmem tests	2015-11-16 15:02:24 -08:00
.gitignore	gitignore: anchor entries at their respective directory	2013-04-02 11:07:52 -07:00
Makefile.in	Prevent rm modules.* when make install	2015-12-02 14:38:20 -08:00