Re: [C/R PATCH] reject checkpoint of fd subject to F_SETSIG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2011-05-02 at 08:18 -0500, Serge Hallyn wrote:
> Quoting Nathan Lynch (ntl@xxxxxxxxx):
> > Similar to our handling of fds that have been subject to F_SETOWN,
> > detect when an fd has had its f_owner->signum changed from the
> > default.
> > 
> > Signed-off-by: Nathan Lynch <ntl@xxxxxxxxx>
> 
> Hey Nathan,
> 
> Can you give more motivation for this?  Do you just feel that it
> isn't worth the risk of mis-coding the check at restart?

The principle here is that we should try to catch at checkpoint time
that which we don't handle correctly at restart.  Right now checkpoint
apparently succeeds, but doing a fcntl(F_GETSIG) after a restart will
show that the signal set before checkpoint has not been preserved.


> For safety check, what about forcing such a task to be restarted
> in a private pidns?

Sorry, I'm not making the connection between this concern and F_SETSIG
and F_GETSIG.  



_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/containers


[Index of Archives]     [Cgroups]     [Netdev]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux