Hi, all: I think it is a BUG, so I report it here. root@1234dahua:~# uname -a Linux 1234dahua 2.6.31.6 #14 Tue Dec 8 16:48:40 CST 2009 ppc unknown Unable to handle kernel paging request for data at a
huh, I don't think I've ever seen an oops here, nor has kerneloops.org. I wonder how you managed this ... :) so this is freeing blocks and adding them to the freespace btrees; it needs to move entrie
2009/12/9 Eric Sandeen <sandeen@xxxxxxxxxxx>: Thanks for your replay. I made this conclusion from assembly code, correct me if I am wrong. <snip> c019e964 <xfs_btree_make_block_unfull>: c019e964: 94
Ok, let's keep this on the list please ... After the first oops I think the rest is not interesting, things are in bad shape by now. Perhaps, but if this is the 2nd oops I think it is not worth inves
Hi, Eric: I add some code like this: if (*stat) { printk("*stat = 0x%08x, oindex = %p, index = %p\n", *stat, oindex, index); if (oindex == NULL || index == NULL) { printk("BUG occured!\n"); printk("o
2009/12/15 hank peng <pengxihan@xxxxxxxxx>: This is what gdb shows: (gdb) list *xfs_btree_make_block_unfull+0xe4 0xc019f568 is in xfs_btree_make_block_unfull (fs/xfs/xfs_btree.c:2650). 2645 if (oinde
This won't catch bad non-NULL pointers like you are seeing. Given that oindex and index are stack varibles, this indicates some thing is probably smashing the stack. Possibly a buffer overrun. To nar
2009/12/15 Dave Chinner <david@xxxxxxxxxxxxx>: Thanks for your reply! As you said, I added some code like this: /* First, try shifting an entry to the right neighbor. */ printk("%s: before xfs_btree_
Are you using any of the xfs userspace prior to this error, or is it a fresh boot and just normal IO? I ask because libxfs calls sys_ustat() which at one point was corrupting userspace, at least, wit
2009/12/15 Eric Sandeen <sandeen@xxxxxxxxxxx>: no xfs userspace prior to this error, just normal IO. Besides, it need some time to produce the OOPS. Forgot to say, I use "-o inode64" when mount. Linu
2009/12/15 Dave Chinner <david@xxxxxxxxxxxxx>: In xfs_btree_make_block_unfull, it seems that oindex and index are optimised to register variables. So, it become more odd. -- The simplest is not all b
2009/12/15 Dave Chinner <david@xxxxxxxxxxxxx>: I added the following debug code as you said: <code> printk("%s: before xfs_btree_rshift, oindex = %p, index = %p\n", __func__, oindex, index); error =