Hi Pedro,
Could you please verfiy that if the commit work for you?
This commit[1] has been merged during 3.11-rc7.
-liubo
commit b8d0c69b9469ffd33df30fee3e990f2d4aa68a09
Author: Josef Bacik
Date: Thu Aug 22 17:03:29 2013 -0400
Btrfs: remove ourselves from the cluster list under lock
Hi Liu,
Sorry, somehow I missed your email.
Let me know if you need additional information. Here's the result of "objdump -d -S"
nearby "run_clustered_refs+0x877":
c12a854f: 83 c4 0cadd$0xc,%esp
c12a8552: eb 3f jmpc12a8593
* a node might live in
On Sat, Nov 09, 2013 at 09:30:50AM -0800, Pedro Fonseca wrote:
> Hi,
>
> I've encountered a bug that triggers a warning message ("list_del
> corruption. next->prev should be d9d0ae28, but was d9d5d5e8") and
> subsequently causes a null pointer dereference while running a
> custom test case on btrf
Hi,
Does anyone have an idea about what could be causing this null pointer bug?
Pedro
On 11/09/2013 06:30 PM, Pedro Fonseca wrote:
Hi,
I've encountered a bug that triggers a warning message ("list_del
corruption. next->prev should be d9d0ae28, but was d9d5d5e8") and
subsequently causes a n
Hi,
I've encountered a bug that triggers a warning message ("list_del
corruption. next->prev should be d9d0ae28, but was d9d5d5e8") and
subsequently causes a null pointer dereference while running a custom
test case on btrfs (kernel 3.11.1), inside a QEMU based VM.
The bug was triggered duri
