Re: [PATCH v8 11/14] lockdep: Apply crossrelease to PG_locked locks

2017-09-04 Thread Byungchul Park
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 contex

Re: [PATCH v8 11/14] lockdep: Apply crossrelease to PG_locked locks

2017-08-10 Thread Peter Zijlstra
On Thu, Aug 10, 2017 at 10:35:02AM +0900, Byungchul Park wrote: > 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_pag

Re: [PATCH v8 11/14] lockdep: Apply crossrelease to PG_locked locks

2017-08-09 Thread Byungchul Park
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 contex

Re: [PATCH v8 11/14] lockdep: Apply crossrelease to PG_locked locks

2017-08-07 Thread kbuild test robot
Hi Byungchul, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170807] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Byungchul-Park/lockdep-Implement-cross