On Wednesday 18 October 2006 20:37, Jeff Dike wrote: > On Tue, Oct 17, 2006 at 11:27:11PM +0200, Paolo 'Blaisorblade' Giarrusso wrote: > > Reimplement execvp for our purposes - after we call fork() it is > > fundamentally unsafe to use the kernel allocator - current is not valid > > there. > > This is horriby ugly. Can we instead do something different like > check out the paths of helpers at early boot, before the kernel is > running, save them, and simply execve them later? > > At that point, something like running "which foo" would be fine by me.
I'd add that this can IMHO cause hard-to-diagnose crashes (I've seen strange behaviours in debug mode, and even schedule-while-atomic warnings, maybe because the creator thread had gone in atomic mode), and since this is a working fix, either this or a replacement should go in. -- Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!". Paolo Giarrusso, aka Blaisorblade http://www.user-mode-linux.org/~blaisorblade Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
