> backtrace: > [<ffffffff8061c162>] kmemleak_alloc_page+0x1eb/0x380 > [<ffffffff80276ae8>] __pagevec_lru_add_active+0xb6/0x104 > [<ffffffff80276b85>] lru_cache_add_active+0x4f/0x53 > [<ffffffff8027d182>] do_wp_page+0x355/0x6f6 > [<ffffffff8027eef1>] handle_mm_fault+0x62b/0x77c > [<ffffffff80632557>] do_page_fault+0x3c7/0xba0 > [<ffffffff8062fb79>] error_exit+0x0/0x51 > [<ffffffffffffffff>] 0xffffffffffffffff > > and > > backtrace: > [<ffffffff8061c162>] kmemleak_alloc_page+0x1eb/0x380 > [<ffffffff80276ae8>] __pagevec_lru_add_active+0xb6/0x104 > [<ffffffff80276b85>] lru_cache_add_active+0x4f/0x53 > [<ffffffff8027eddc>] handle_mm_fault+0x516/0x77c > [<ffffffff8027f180>] get_user_pages+0x13e/0x462 > [<ffffffff802a2f65>] get_arg_page+0x6a/0xca > [<ffffffff802a30bf>] copy_strings+0xfa/0x1d4 > [<ffffffff802a31c7>] copy_strings_kernel+0x2e/0x43 > [<ffffffff802d33fb>] compat_do_execve+0x1fa/0x2fd > [<ffffffff8021e405>] sys32_execve+0x44/0x62 > [<ffffffff8021def5>] ia32_ptregs_common+0x25/0x50 > [<ffffffffffffffff>] 0xffffffffffffffff > > I'll dig into them further, but do either of these look like known issues? no known issue. AFAIK, 2.6.27 - 2.6.33 don't have such problem. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>