public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ext3 lockdep warning in 2.6.25-rc6
Date: Sun, 23 Mar 2008 12:06:27 +0100	[thread overview]
Message-ID: <1206270388.6437.90.camel@lappy> (raw)
In-Reply-To: <200803222234.m2MMYRJo005108@agora.fsl.cs.sunysb.edu>

On Sat, 2008-03-22 at 18:34 -0400, Erez Zadok wrote:
> In message <1206207527.6437.83.camel@lappy>, 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?

Its a generic problem with drop_caches. If you look in the lkml archives
you'll find similar reports against XFS and others.

Some time ago Andrew outlined a fix for it, but so far that hasn't
happened:  http://lkml.org/lkml/2007/2/23/46




  reply	other threads:[~2008-03-23 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 14:37 ext3 lockdep warning in 2.6.25-rc6 Erez Zadok
2008-03-22 17:38 ` Peter Zijlstra
2008-03-22 22:34   ` Erez Zadok
2008-03-23 11:06     ` Peter Zijlstra [this message]
2008-03-25 18:29 ` Jan Kara
2008-04-01 21:23   ` Erez Zadok
2008-04-02  8:12     ` Jan Kara
2008-04-02 16:34       ` Erez Zadok
2008-04-04  3:14       ` David Chinner
2008-04-04 15:37   ` Erez Zadok
2008-04-07 11:47     ` Jan Kara

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=1206270388.6437.90.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=adilger@clusterfs.com \
    --cc=akpm@linux-foundation.org \
    --cc=ezk@cs.sunysb.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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