On 12/10/13 14:25 , Chris Mason wrote:
Quoting Pedro Fonseca (2013-12-09 16:15:46)
Hi,
I've got multiple instances of warnings caused by the statement
"WARN_ON(!(entry->vfs_inode.i_state & (I_WILL_FREE | I_FREEING)));" in
inode_tree_add(). The tests were executed
Hi,
I've got multiple instances of warnings caused by the statement
"WARN_ON(!(entry->vfs_inode.i_state & (I_WILL_FREE | I_FREEING)));" in
inode_tree_add(). The tests were executed on the official 3.12.2 kernel.
Do you think it's something serious?
Pedro
Warning message (for test 1):
[
entry+0x4/0x71 SS:ESP
0068:deed7ca4
[ 532.060786] CR2:
[ 532.060786] ---[ end trace 39d9898f10bcb730 ]---
On 12/6/13 3:09 PM, Pedro Fonseca wrote:
On 12/06/2013 02:58 PM, Liu Bo wrote:
On Fri, Dec 06, 2013 at 02:01:25PM +0100, Pedro Fonseca wrote:
Hi,
I've encountere
On 12/06/2013 02:58 PM, Liu Bo wrote:
On Fri, Dec 06, 2013 at 02:01:25PM +0100, Pedro Fonseca wrote:
Hi,
I've encountered another null pointer bug in btrfs_find_all_root().
It may be releated to a bug I previously reported to the mailing
list ("Null pointer derefere
Hi,
I've encountered another null pointer bug in btrfs_find_all_root().
It may be releated to a bug I previously reported to the mailing list
("Null pointer dereference bug in btrfs_find_all_root"). But this test
ran on kernel version 3.12.2 and the oops was triggered when deleting an
item fr
Hi,
I've been getting the error message "fs tree 264 refs 1 not found" when
running btrfsck (v0.19) after a test case. The test case creates and
then deletes a subvolume while concurrently creating a snapshot of the
parent directory. This situation occurred with kernel version 3.11.1.
Here's
Hi,
In another test, I've encountered a few situations that triggered a warning message in "record_one_backref()". I'm not sure if it's serious but it is probably related to
the concurrent defragment operations executed during the test.
Warning dump:
[ 147.558178] [ cut here ]---
edro
On 11/14/13 03:46 , Liu Bo wrote:
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 poin
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
sub
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
On 10/29/2013 07:17 AM, Liu Bo wrote:
On Tue, Oct 29, 2013 at 04:38:39AM +0100, Pedro Fonseca wrote:
On 10/29/13 3:05 AM, Liu Bo wrote:
Hi,
On Mon, Oct 28, 2013 at 05:02:11PM +0100, Pedro Fonseca wrote:
Hi,
I've encountered a few NULL pointer dereference bugs while running a
custom
On 10/29/13 3:05 AM, Liu Bo wrote:
Hi,
On Mon, Oct 28, 2013 at 05:02:11PM +0100, Pedro Fonseca wrote:
Hi,
I've encountered a few NULL pointer dereference bugs while running a
custom test case on btrfs (kernel 3.11.1), inside a QEMU based VM.
Btrfs was statically compiled and the
Hi,
I've encountered a few NULL pointer dereference bugs while running a
custom test case on btrfs (kernel 3.11.1), inside a QEMU based VM.
Btrfs was statically compiled and the btrfs filesystem was mounted on
one or two loop devices. All cases occurred during execution of a
"filesystem bala
13 matches
Mail list logo
