From: Miao Xie <miaox@cn.fujitsu.com>
To: Geert Jansen <geertj@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: list_del corruption
Date: Mon, 23 Dec 2013 18:18:34 +0800 [thread overview]
Message-ID: <52B80DFA.5060409@cn.fujitsu.com> (raw)
In-Reply-To: <CADbA=FVN5juGTxFZKdj_gqmJ5aGSyzikXMW9HDUAciBX1mUWzg@mail.gmail.com>
On mon, 23 Dec 2013 09:49:16 +0100, Geert Jansen wrote:
> Hi,
>
> myself, and some other Fedora users, are experiencing a crash in
> btrfs. I am using Fedora 20 with its stock kernel (3.12.5 based). The
> call trace is here:
>
> https://retrace.fedoraproject.org/faf/reports/226666/
>
> I have no way to reproduce unfortunately. The crash happens about once a week.
>
> There is also a Red Hat bugzilla here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1028750
>
> The Red Hat bugzilla contains a patch for 3.13 that is claimed to fix
> the issue. However the patch does not apply cleanly, and the comment
> in the patch indicate that it fixes a different, more recently
> introduced bug.
>
> Any help is appreciated.
It should be fixed by:
commit 93858769172c4e3678917810e9d5de360eb991cc
Author: Josef Bacik <jbacik@fusionio.com>
Date: Mon Oct 28 09:13:25 2013 -0400
Btrfs: take ordered root lock when removing ordered operations inode
A user reported a list corruption warning from btrfs_remove_ordered_extent, it
is because we aren't taking the ordered_root_lock when we remove the inode from
the ordered operations list. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Thanks
Miao
>
> Thanks,
> Geert Jansen
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-12-23 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 8:49 list_del corruption Geert Jansen
2013-12-23 10:18 ` Miao Xie [this message]
2013-12-23 18:58 ` Chris Murphy
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=52B80DFA.5060409@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=geertj@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.