Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[BUG\s+report\]xfs_btree_make_block_unfull\s+generated\s+an\s+OOPS\s*$/: 12 ]

Total 12 documents matching your query.

1. [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Wed, 9 Dec 2009 09:58:44 +0800
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
/archives/xfs/2009-12/msg00073.html (9,955 bytes)

2. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 08 Dec 2009 20:57:21 -0600
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
/archives/xfs/2009-12/msg00074.html (11,412 bytes)

3. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Wed, 9 Dec 2009 11:18:49 +0800
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
/archives/xfs/2009-12/msg00075.html (16,520 bytes)

4. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 14 Dec 2009 09:56:59 -0600
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
/archives/xfs/2009-12/msg00121.html (20,030 bytes)

5. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Tue, 15 Dec 2009 08:49:37 +0800
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
/archives/xfs/2009-12/msg00139.html (26,835 bytes)

6. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Tue, 15 Dec 2009 08:58:15 +0800
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
/archives/xfs/2009-12/msg00140.html (30,015 bytes)

7. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Tue, 15 Dec 2009 12:26:40 +1100
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
/archives/xfs/2009-12/msg00141.html (12,821 bytes)

8. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Tue, 15 Dec 2009 09:56:32 +0800
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_
/archives/xfs/2009-12/msg00142.html (16,704 bytes)

9. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 14 Dec 2009 21:15:09 -0600
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
/archives/xfs/2009-12/msg00143.html (16,928 bytes)

10. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Tue, 15 Dec 2009 11:22:59 +0800
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
/archives/xfs/2009-12/msg00144.html (20,921 bytes)

11. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Tue, 15 Dec 2009 13:36:29 +0800
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
/archives/xfs/2009-12/msg00148.html (14,988 bytes)

12. Re: [BUG report]xfs_btree_make_block_unfull generated an OOPS (score: 1)
Author: hank peng <pengxihan@xxxxxxxxx>
Date: Wed, 13 Jan 2010 09:11:02 +0800
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 =
/archives/xfs/2010-01/msg00200.html (18,626 bytes)


This search system is powered by Namazu