Zachary Amsden wrote: > Note you can always run out of space; to ensure safety, the init code > needs to not use a fixed mapping size, it needs to map > end_kernel_address + pae ? 1808k : 896k, assuming 128M vmalloc hole. > This could cause problems like running into initrd, however, so might > require loader changes, or perhaps relocating the initrd. Is the > solution to just cap the kernel size at some fixed maximum? 6.2M > appears to be the safe limit for all configurations. > > I'm pulling this back onto lkml; seems this is a serious bug which > needs attention. I've also cc'd some parties that might have relevant > knowledge. Why do I seem to recall head.S mapping 128M of mappings at > one point in time?
I just posted a patch. Oops, forgot to Cc: Eric. J - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/