From: coLinux a. <col...@he...> - 2008-04-16 04:12:33
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080415/ colinux-0.8.0-20080415.src.tgz (677833 Bytes) daemons-0.8.0-20080415.dbg.zip (1314717 Bytes) daemons-0.8.0-20080415.zip (1020545 Bytes) modules-2.6.22.18-co-0.8.0-20080415.tgz (2600435 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080415.zip (1762539 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20080415.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1017 | henryn | 2008-04-15 21:03:09 +0000 (Tue, 15 Apr 2008) | 22 lines Changed paths: M /branches/devel/NEWS M /branches/devel/patch/base-2.6.22.diff * Bug fix for randomly crashes on coLinux boot, mostly with initrd. Some machines with ext2 or ext3 (not reisserfs) for the root file system coLinux was faulting with host reboot or freeze. Some machines works better without initrd, because every mount was a risk for crashing. A page fault in do_page_fault handler from calling sys_mount with params from kernel address space was detected as problem. (Thanks Paolo) Exactly "pte_present(*pte_k)" in vmalloc_fault() was triple or more recursively faulting with stack overflow. A candidate for such badly pointers was the function mount_block_root(). There an one page allocated variable "fs_names" was later tried to read 4096 bytes +9 behind the end in the function exact_copy_from_user(). The vmalloc_fault() was trying to map the page behind this end. But, if there is no page, then it should fault, that's what exact_copy_from_user assumed. The address will check in vmalloc range between VMALLOC_START and VMALLOC_END now, before accessing the PTE macros. * The added lines are ported from 64 bit source of kernel 2.6.25-rc9. ------------------------------------------------------------------------ |