From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: sync-related lockdep warnings
Date: Wed, 17 Dec 2008 11:03:27 -0500 [thread overview]
Message-ID: <1229529807.27170.34.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1229374883.16295.27.camel@think.oraclecorp.com>
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
prev parent reply other threads:[~2008-12-17 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 19:01 sync-related lockdep warnings Sage Weil
2008-12-15 19:42 ` Chris Mason
2008-12-15 21:01 ` Chris Mason
2008-12-17 16:03 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1229529807.27170.34.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox