On Thu, Jan 05, 2023 at 11:24:29AM -1000, Tejun Heo wrote: > Holding the queue lock now implies RCU read lock, so no need to use > rcu_read_[un]lock() explicitly. This shouldn't cause any behavior changes. How so? > While at it, drop __acquires() annotation on the queue lock too. The > __acquires() part was already out of sync and it doesn't catch anything that > lockdep can't. This makes sparse even more unhappy than it was before. For now please keep the annotation.
