From: BlaisorBlade <bla...@ya...> - 2003-12-26 19:02:17
|
Alle 19:27, venerd=EC 26 dicembre 2003, Cameron Patrick ha scritto: > On Fri, Dec 26, 2003 at 07:05:48PM +0100, BlaisorBlade wrote: > | Go here: > | > | http://web.tiscali.it/no-redirect-tiscali/blaisorblade/index.html > > Which says: > > The only problematic patch is A-04-MM-compile-fix.patch, but > maybe i386 can live even with it (I don't remember if I got a > successful compilation with it applied). However, I think it's > not at all safe even if it compiles. > > and in the README: > > but I think you'd better avoid doing this or do a complete > backup, since you'll need it...). > Eeek! I just upgraded my home desktop to a 2.6.0 kernel with that patch > applied (actually as part of Jeff's 2.6.0-test9 patch) and so far it > seems to be working. Are you sure? If you compile a stock 2.6.0 with Jeff's 2.6.0-test9 patch an= d=20 try to compile an i386 kernel, you'll get soon errors about=20 do_mmap_pgoff(except if you applied a host-skas to your 2.6 tree). > Looking at the patch, it seems innocuous enough - > why should it be unsafe on an i386 kernel? I don't know actually, but it doesn't seem innocuous. Instead, FIXADDR_USER_START is replaced by FIXADDR_START(+ some syntactical= =20 changes that do not hurt). And they have a different meaning(see=20 include/asm-i386/fixmap.h). Since I'm not a VM hacker, and I don't understand the change, I just say th= at=20 that shouldn't be used, for prudence's sake. That mention about backup is=20 maybe a bit exaggerated, but it's a form of "no warranty" disclaimer. *NOTE*: the combo patches from Ingo Molnar contain this, too(I don't know i= f=20 he noticed this change at all), and he probably used this without problem. = So=20 I may be wrong at all. Bye =2D-=20 cat <<EOSIGN Paolo Giarrusso, aka Blaisorblade Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729 EOSIGN |