On Mon, 29 Mar 2010, Carlos O'Donell wrote: > > I got a kernel to boot which shouldn't clobber r19. Turned out to > > be a typo. This uses PT_SR4 for the kernel return for the child. > > Will test with gcc build. > > > > Will try again using the pad0 field later. > > Sorry, what turned out to be a typo? I used PT_SR4 instead of TASK_PT_SR4 in child_return ;( > I guess any static binary that calls fork/vfork/clone is susceptible > to corruption of r19 in this way. > > I don't know how much that effects userspace, since most is shared, > *however* the dynamic linker is technically a static binary :-) The change may not fix much, but there's no technical reason that the kernel needs to clobber r19. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
