| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 15 Nov 2006 07:32:31 -0800 From: "Martin J. Bligh" <mbligh@...igh.org> To: Hugh Dickins <hugh@...itas.com> Cc: Andrew Morton <akpm@...l.org>, Mel Gorman <mel@...net.ie>, linux-kernel@...r.kernel.org Subject: Re: Boot failure with ext2 and initrds Hugh Dickins wrote: > On Tue, 14 Nov 2006, Hugh Dickins wrote: >> On Tue, 14 Nov 2006, Andrew Morton wrote: >>> The below might help. >> Indeed it does (with Martin's E2FSBLK warning fix), >> seems to be running well on all machines now. > > i386 and ppc64 still doing builds, but after an hour on x86_64, > an ld got stuck in a loop under ext2_try_to_allocate_with_rsv, > alternating between ext2_rsv_window_add and rsv_window_remove. Ugh. What test are you doing? kernel compile in a tight loop forever? Andrew, do you want to drop the set for now, and we can try and debug it outside of -mm? No reason to break your tree if we don't have to ... > Send me a patch and I'll try it... > > ext2_try_to_allocate_with_rsv+0x288 > ext2_new_blocks+0x21e > ext2_get_blocks+0x398 > ext2_get_block+0x46 > __block_prepare_write+0x171 > block_prepare_write+0x39 > ext2_prepare_write+0x2c > generic_file_buffered_write+0x2b0 > __generic_file_aio_write_nolock+0x4bc > generic_file_aio_write+0x6d > do_sync_write+0xf9 > vfs_write+0xc8 > sys_write+0x51 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists