Re: sysfs_bin_mmap lockdep trace.

2013-11-14 Thread Dave Jones
On Thu, Nov 14, 2013 at 02:41:16PM +0900, Tejun Heo wrote: > hey, > > On Wed, Nov 13, 2013 at 08:10:43PM +, Al Viro wrote: > > On Wed, Nov 13, 2013 at 01:45:38PM -0500, Dave Jones wrote: > > > Al, is this one also known ? Also seen on v3.12-7033-g42a2d923cc34 > > > > Umm... I've seen

Re: sysfs_bin_mmap lockdep trace.

2013-11-13 Thread Tejun Heo
hey, On Wed, Nov 13, 2013 at 08:10:43PM +, Al Viro wrote: > On Wed, Nov 13, 2013 at 01:45:38PM -0500, Dave Jones wrote: > > Al, is this one also known ? Also seen on v3.12-7033-g42a2d923cc34 > > Umm... I've seen something like that reported after sysfs merge went in > (right after 3.12), but

Re: sysfs_bin_mmap lockdep trace.

2013-11-13 Thread Al Viro
On Wed, Nov 13, 2013 at 01:45:38PM -0500, Dave Jones wrote: > Al, is this one also known ? Also seen on v3.12-7033-g42a2d923cc34 Umm... I've seen something like that reported after sysfs merge went in (right after 3.12), but I hadn't looked into details. > -> #3 (&mm->mmap_sem){++}:

sysfs_bin_mmap lockdep trace.

2013-11-13 Thread Dave Jones
Al, is this one also known ? Also seen on v3.12-7033-g42a2d923cc34 == [ INFO: possible circular locking dependency detected ] 3.12.0+ #2 Not tainted --- trinity-child0/9004 is trying to acquire