OpenVZ Forum


Home » Mailing lists » Devel » [RFC,PATCH] fix /sbin/init signal handling
Re: [RFC,PATCH] fix /sbin/init signal handling [message #19738 is a reply to message #19735] Tue, 21 August 2007 10:30 Go to previous messageGo to previous message
Oleg Nesterov is currently offline  Oleg Nesterov
Messages: 143
Registered: August 2006
Senior Member
On 08/21, sukadev@us.ibm.com wrote:
> 
> I am still reviewing this patch and will try to plug in the multiple
> pid ns code and play with it some more in the next couple of days.

Thanks!

> But am curious why we need the in_interrupt() check and that too only
> for the container-init process.

For example, send_sigio(). We shouldn't send this signal to /sbin/init.
But what if the interrupted process is from the parent namespace?

> Also, maybe a dumb que, are the checks for SIG_IGN and SIG_DFL required
> both on sender side and the receiver side (get_signal_to_deliver())

get_signal_to_deliver() checks SIG_IGN/SIG_DFL, but I guess you meant
a special check for init.

Unless the patch is wrong, this is not needed. And, in fact we can't do
this anyway. Because get_signal_to_deliver() can't know if the signal
comes from parent namespace or not.

Oleg.

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH 13/14] sysfs: Rewrite rename in terms of sysfs dirents
Next Topic: Re: [PATCHSET] Sysfs cleanups from Eric W. Biederman
Goto Forum:
  


Current Time: Sat Oct 25 14:54:05 GMT 2025

Total time taken to generate the page: 0.08424 seconds