public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: btrfs: warn_slowpath in clean_tree_block and others
Date: Wed, 25 Feb 2009 13:36:26 -0500	[thread overview]
Message-ID: <1235586986.32346.48.camel@think.oraclecorp.com> (raw)
In-Reply-To: <20090224230249.GA6859@vlad.carfax.org.uk>

On Tue, 2009-02-24 at 23:02 +0000, Hugo Mills wrote:
> This is essentially a repost of a mail I made last week, to which I
> didn't get a reply.
> 

Sorry I missed replying to this one last week, thanks for resending.

>    I'm getting huge numbers of kernel warnings whilst using
> btrfs. They're all "warn_slowpath", and all seem to be in
> fs/btrfs/disk-io.c. I've included one typical example at the end of
> this mail.
> 
>    Kernel versions are 2.6.29-rc2, -rc4 and -rc6.
> 

The warnings look like i386, exactly what hardware is this?  Is your
kernel compiled for SMP or UP?

The warning you're getting is that clean_tree_block expects this block
to be locked, and giving out a warning because it is showing up as
unlocked.

So, hopefully you're on a UP kernel and my test for a locked spinlock is
broken in that config.

-chris



  parent reply	other threads:[~2009-02-25 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 23:02 btrfs: warn_slowpath in clean_tree_block and others Hugo Mills
2009-02-25  4:22 ` Mitch Harder (aka DontPanic)
2009-02-25  6:26   ` Lee Trager
2009-02-25 18:36 ` Chris Mason [this message]
2009-02-25 18:54   ` Hugo Mills

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=1235586986.32346.48.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=hugo-lkml@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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