From: Chris Mason <chris.mason@oracle.com>
To: "Mitch Harder (aka DontPanic)" <mmharder@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: warn_slowpath in clean_tree_block and others
Date: Wed, 25 Feb 2009 14:26:43 -0500 [thread overview]
Message-ID: <1235590003.32346.61.camel@think.oraclecorp.com> (raw)
In-Reply-To: <89ed0c690902251050g1e6dd23ay5d5426adb7086018@mail.gmail.com>
[ resend with the list cc'd ]
On Wed, 2009-02-25 at 12:50 -0600, Mitch Harder (aka DontPanic) wrote:
> I'll try to test that out.
>
> I had just noticed that some of my kernel configuration settings (not
> sure which ones) seem to affect the clean_tree_block warnings I've
> been getting, and one of my customizations is usually to configure the
> kernel for a single processor.
>
I'll push out a patch tonight that fixes things, the code to test for a
locked buffer is just broken on UP. For now, the patch below will do:
diff --git a/fs/btrfs/locking.c b/fs/btrfs/locking.c
index 85506c4..4513ecf 100644
--- a/fs/btrfs/locking.c
+++ b/fs/btrfs/locking.c
@@ -222,6 +222,5 @@ int btrfs_tree_unlock(struct extent_buffer *eb)
int btrfs_tree_locked(struct extent_buffer *eb)
{
- return test_bit(EXTENT_BUFFER_BLOCKING, &eb->bflags) ||
- spin_is_locked(&eb->lock);
+ return 1;
}
next prev parent reply other threads:[~2009-02-25 19:26 UTC|newest]
Thread overview: 10+ 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
[not found] ` <89ed0c690902250603g2f6236d6q3be2f2f065ea0df@mail.gmail.com>
2009-02-25 16:05 ` Lee Trager
2009-02-25 16:13 ` Hugo Mills
2009-02-25 16:16 ` Mitch Harder (aka DontPanic)
2009-02-25 18:36 ` Chris Mason
2009-02-25 18:54 ` Hugo Mills
[not found] ` <89ed0c690902251050g1e6dd23ay5d5426adb7086018@mail.gmail.com>
2009-02-25 19:26 ` Chris Mason [this message]
2009-02-25 21:41 ` 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=1235590003.32346.61.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mmharder@gmail.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