On Mon, Aug 07, 2017 at 04:12:58PM +0900, Byungchul Park wrote: > Although lock_page() and its family can cause deadlock, the lock > correctness validator could not be applied to them until now, becasue > things like unlock_page() might be called in a different context from > the acquisition context, which violates lockdep's assumption. > > Thanks to CONFIG_LOCKDEP_CROSSRELEASE, we can now apply the lockdep > detector to page locks. Applied it.
Is there any reason excluding applying it into PG_locked?
