padata: Fix wrong usage of rcu_dereference()
authorMathias Krause <minipli@googlemail.com>
Thu, 28 Nov 2013 18:20:05 +0000 (19:20 +0100)
committerHerbert Xu <herbert@gondor.apana.org.au>
Thu, 5 Dec 2013 13:28:42 +0000 (21:28 +0800)
commitc0e656b7a6e1ac03b2921d49211a735893efd544
tree3c395a0346da235564b23b50d4dab8b9f81b28f1
parent3110e4006ca9652276c2e17443949bcba7dbe789
padata: Fix wrong usage of rcu_dereference()

A kernel with enabled lockdep complains about the wrong usage of
rcu_dereference() under a rcu_read_lock_bh() protected region.

  ===============================
  [ INFO: suspicious RCU usage. ]
  3.13.0-rc1+ #126 Not tainted
  -------------------------------
  linux/kernel/padata.c:115 suspicious rcu_dereference_check() usage!

  other info that might help us debug this:

  rcu_scheduler_active = 1, debug_locks = 1
  1 lock held by cryptomgr_test/153:
   #0:  (rcu_read_lock_bh){.+....}, at: [<ffffffff8115c235>] padata_do_parallel+0x5/0x270

Fix that by using rcu_dereference_bh() instead.

Signed-off-by: Mathias Krause <minipli@googlemail.com>
Acked-by: Steffen Klassert <steffen.klassert@secunet.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
kernel/padata.c