On 10/14, Oleg Nesterov wrote: > > On 10/13, Oleg Nesterov wrote: > > > > Please review, this series fixes the serious bug reported by > > Martin and David and cc's stable. See the changelog in 5/5.
OK, nobody seems to object, I am going to ask Ingo to pull this fix. But, > This probably needs another patch to handle the special case, vfork(). > In this case it would be more correct to dup return_instances but > (obviously) avoid dup_xol_area. > > However I think this is not that important, the child should not "unwind" > the stack if it shares mm/stack with its parent, otherwise it can corrupt > the parent's stack. Yes, but I forgot that at least the child should return from vfork() itself and it can be ret-probed. So I am sending the additional 6/5 in reply to 0/5. This change can be joined with 1/5, but I'd prefer to do this in a separate patch for better documentation. Oleg. -- 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/
