Re: [PATCH 1/4] mm: fix invalidate_complete_page2 lock ordering

2012-09-21 Thread Mel Gorman
On Tue, Sep 18, 2012 at 08:51:47PM -0700, Hugh Dickins wrote: > In fuzzing with trinity, lockdep protested "possible irq lock inversion > dependency detected" when isolate_lru_page() reenabled interrupts while > still holding the supposedly irq-safe tree_lock: > > invalidate_inode_pages2 > inval

Re: [PATCH 1/4] mm: fix invalidate_complete_page2 lock ordering

2012-09-19 Thread Johannes Weiner
On Tue, Sep 18, 2012 at 08:51:47PM -0700, Hugh Dickins wrote: > In fuzzing with trinity, lockdep protested "possible irq lock inversion > dependency detected" when isolate_lru_page() reenabled interrupts while > still holding the supposedly irq-safe tree_lock: > > invalidate_inode_pages2 > inval

[PATCH 1/4] mm: fix invalidate_complete_page2 lock ordering

2012-09-18 Thread Hugh Dickins
In fuzzing with trinity, lockdep protested "possible irq lock inversion dependency detected" when isolate_lru_page() reenabled interrupts while still holding the supposedly irq-safe tree_lock: invalidate_inode_pages2 invalidate_complete_page2 spin_lock_irq(&mapping->tree_lock) clear_page