* sync-related lockdep warnings
@ 2008-12-15 19:01 Sage Weil
2008-12-15 19:42 ` Chris Mason
2008-12-15 21:01 ` Chris Mason
0 siblings, 2 replies; 4+ messages in thread
From: Sage Weil @ 2008-12-15 19:01 UTC (permalink / raw)
To: linux-btrfs
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...
sage
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sync-related lockdep warnings
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
1 sibling, 0 replies; 4+ messages in thread
From: Chris Mason @ 2008-12-15 19:42 UTC (permalink / raw)
To: Sage Weil; +Cc: linux-btrfs
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...
Thanks. I think this is harmless, but I don't actually need do disable
irqs on the delalloc lock. So, I'm doing some testing here with a
non-irq variant.
-chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sync-related lockdep warnings
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
1 sibling, 1 reply; 4+ messages in thread
From: Chris Mason @ 2008-12-15 21:01 UTC (permalink / raw)
To: Sage Weil; +Cc: linux-btrfs
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.
Thanks,
Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: sync-related lockdep warnings
2008-12-15 21:01 ` Chris Mason
@ 2008-12-17 16:03 ` Chris Mason
0 siblings, 0 replies; 4+ messages in thread
From: Chris Mason @ 2008-12-17 16:03 UTC (permalink / raw)
To: Sage Weil; +Cc: linux-btrfs
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-12-17 16:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.