From: Li Zefan <lizf@cn.fujitsu.com>
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: Linux BTRFS <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>,
Josef Bacik <josef@redhat.com>
Subject: Re: 2.6.38 defragment compression oops...
Date: Mon, 28 Mar 2011 14:58:04 +0800 [thread overview]
Message-ID: <4D90317C.8040409@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTin5EKNYUVwUMO+PoJyuEBVxubUuAHfu-ue4w+7n@mail.gmail.com>
Daniel J Blueman wrote:
> I found that I'm able to provoke undefined behaviour with 2.6.38 with
> extent defragmenting + recompression, eg:
>
> mkfs.btrfs /dev/sdb
> mount /dev/sdb /mnt
> cp -xa / /mnt
> find /mnt -print0 | xargs -0 btrfs filesystem defragment -vc
>
> After a short time, I was seeing what looked like a secondary effect
> [1]. Reproducing with lock instrumentation reported recursive spinlock
> acquisition, probably a false-positive from the locking scheme not
> being annotated, so better report it now.
>
Thanks for the report! I'll investigate this.
prev parent reply other threads:[~2011-03-28 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 9:00 2.6.38 defragment compression oops Daniel J Blueman
2011-03-28 6:58 ` Li Zefan [this message]
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=4D90317C.8040409@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=daniel.blueman@gmail.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).