[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200803222234.m2MMYRJo005108@agora.fsl.cs.sunysb.edu>
Date: Sat, 22 Mar 2008 18:34:27 -0400
From: Erez Zadok <ezk@...sunysb.edu>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Erez Zadok <ezk@...sunysb.edu>, sct@...hat.com,
akpm@...ux-foundation.org, adilger@...sterfs.com,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ext3 lockdep warning in 2.6.25-rc6
In message <1206207527.6437.83.camel@...py>, Peter Zijlstra writes:
> On Sat, 2008-03-22 at 10:37 -0400, Erez Zadok wrote:
> > I was building a kernel using "make -j 4" inside a unionfs, mounted on top
> > of ext3. The kernel is vanilla 2.6.25-rc6 plus unionfs patches. At some
> > point I forced a cache flush using "echo 3 > /proc/sys/vm/drop_caches" and I
> > got the lockdep warning below. Note that unionfs doesn't appear to be
> > involved in this lockdep warning at all, so I suspect this is probably an
> > issue between jbd and ext3 directly.
>
> Known issue, drop_caches isn't production quality.
Is this a general problem with drop_caches, or its interaction with
ext3/jbd? If I get a similar lockdep warning with other file systems,
should I bother to report this to the respective f/s maintainers?
Thanks,
Erez.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists