Quoting Eric W. Biederman (ebiederm@xxxxxxxxxxxx): > sukadev@xxxxxxxxxx writes: > > > From: Sukadev Bhattiprolu <sukadev@xxxxxxxxxx> > > Subject: [PATCH] Masquerade sender information > > > > With multiple pid namespaces, sender of a signal could be in an ancestor > > namespace of the receiver and so the sender will not have a valid 'pid_t' > > in the receiver's namespace. > > > > In this case, masquerade the 'siginfo' for the signal to pretend that the > > signal originated from the kernel. > > At first glance this looks ok. I think the only case where we can > be sending a signal from inside a pid namespace to something not > in a child pid namespace is if we are the kernel. In which case Are we now blocking F_SETOWN|F_SETSIG signals to outside our pid namespace? mq_notify? (I didn't think we were) > we also want si_pid = 0. > > If that holds this problem is easier then I was thinking it would > be. > > Eric > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
