On Wed, Oct 14, 2015 at 09:42:58AM -0700, Andy Lutomirski wrote: > > That's the intent. > > If you write __pad = 0, don't set UC_STRICT_RESTORE_SS, and leave cs > set to a 64-bit value, then the kernel will detect that 0 is not a > valid SS and will fix it for you. > > If you do write UC_STRICT_RESTORE_SS (e.g. if you saved on a new > kernel and you restore the saved uc_flags), then you'll get a new > signal delivered.
Yeah, I just wanna be sure I understood the patch correctly. Thanks! > If you're restoring a 32-bit or 16-bit context, then none of the above > applies, but I doubt that CRIU supports that anyway. True. I didn't implemented compat mode for criu yet, it's in todo. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
