From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: sync-related lockdep warnings Date: Wed, 17 Dec 2008 11:03:27 -0500 Message-ID: <1229529807.27170.34.camel@think.oraclecorp.com> References: <1229374883.16295.27.camel@think.oraclecorp.com> Mime-Version: 1.0 Content-Type: text/plain Cc: linux-btrfs@vger.kernel.org To: Sage Weil Return-path: In-Reply-To: <1229374883.16295.27.camel@think.oraclecorp.com> List-ID: On Mon, 2008-12-15 at 16:01 -0500, Chris Mason wrote: > On Mon, 2008-12-15 at 11:01 -0800, Sage Weil wrote: > > Hi- > > > > I've been regularly getting a lockdep warning on inode_lock vs tree->lock. > > It is quickly triggered by my code, which calls ioctl(fd, BTRFS_IOC_SYNC) > > (which just does a btrfs_sync_fs) at regular intervals. > > > > http://ceph.newdream.net/dump/btrfs-lockdep-sync-ioctl.txt > > > > The second warning is similar, but looks to be a bit more revealing. It > > is easily triggered by 'while [ 1 ] ; do sync ; done' and then something > > like 'echo a > a' a few times. > > > > http://ceph.newdream.net/dump/btrfs-lockdep-sync.txt > > > > Let me know if there's any other info on my end that would help sort this > > out... > > If you pull from btrfs-unstable, this should be fixed. Well, not so much fixed as traded for a different lockdep warning of the same time. I've got a new patch in testing here ;) -chris