[BUG]kmalloc memory in reiserfs code failed on a dual amd64/4G linux 2.6.2 box

[lepton]

I seen such dmesg in mu dual amd64/4G memory box.

I am running kernel 2.6.2

This is the second time I saw some problems about __alloc_pages on this
amd 64 box...


sort: page allocation failure. order:1, mode:0x20

Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
       <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
       <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
       <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
       <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff801bd6a8>{pathrelse+40} 
       <ffffffff801a834b>{reiserfs_create+171} <ffffffff8017690c>{vfs_create+140} 
       <ffffffff80176ca8>{open_namei+424} <ffffffff801675a7>{filp_open+39} 
       <ffffffff801210a8>{sys32_open+56} <ffffffff8011e25e>{ia32_do_syscall+30} 
       
sort: page allocation failure. order:1, mode:0x20

Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
       <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
       <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
       <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
       <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff801bd6a8>{pathrelse+40} 
       <ffffffff801a834b>{reiserfs_create+171} <ffffffff8017690c>{vfs_create+140} 
       <ffffffff80176ca8>{open_namei+424} <ffffffff801675a7>{filp_open+39} 
       <ffffffff801210a8>{sys32_open+56} <ffffffff8011e25e>{ia32_do_syscall+30} 
       
sort: page allocation failure. order:1, mode:0x20

Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
       <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
       <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
       <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
       <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff801bd6a8>{pathrelse+40} 
       <ffffffff801a834b>{reiserfs_create+171} <ffffffff8017690c>{vfs_create+140} 
       <ffffffff80176ca8>{open_namei+424} <ffffffff801675a7>{filp_open+39} 
       <ffffffff801210a8>{sys32_open+56} <ffffffff8011e25e>{ia32_do_syscall+30} 
       
sort: page allocation failure. order:1, mode:0x20

Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
       <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
       <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
       <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
       <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff801bd6a8>{pathrelse+40} 
       <ffffffff801a834b>{reiserfs_create+171} <ffffffff8017690c>{vfs_create+140} 
       <ffffffff80176ca8>{open_namei+424} <ffffffff801675a7>{filp_open+39} 
       <ffffffff801210a8>{sys32_open+56} <ffffffff8011e25e>{ia32_do_syscall+30} 
       
sort: page allocation failure. order:1, mode:0x20

Call Trace:<ffffffff8014e5f0>{__alloc_pages+816} <ffffffff8014e65e>{__get_free_pages+78} 
       <ffffffff80151921>{cache_grow+177} <ffffffff80151e78>{cache_alloc_refill+440} 
       <ffffffff801521c6>{__kmalloc+102} <ffffffff801b44f6>{get_mem_for_virtual_node+102} 
       <ffffffff801b49a8>{fix_nodes+232} <ffffffff801c08c5>{reiserfs_insert_item+149} 
       <ffffffff801acf2c>{reiserfs_new_inode+892} <ffffffff8014e2a5>{buffered_rmqueue+325} 
       <ffffffff801bd6a8>{pathrelse+40} <ffffffff801a834b>{reiserfs_create+171} 
       <ffffffff8017690c>{vfs_create+140} <ffffffff80176ca8>{open_namei+424} 
       <ffffffff801675a7>{filp_open+39} <ffffffff801210a8>{sys32_open+56} 
       <ffffffff8011e25e>{ia32_do_syscall+30} 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/