Nathan Lynch wrote: > Oren Laadan <orenl@xxxxxxxxxxxxxxx> writes: >> What happens if we checkpoint on a system with CONFIG_FUTEX and >> restart on a a system with !CONFIG_FUTEX ? > > You can't disable FUTEX unless EMBEDDED=y, and EMBEDDED is the "I know > what I'm doing" knob. Is this really worth worrying about? > Good point. Still, a warning won't hurt, and can be done in userspace. Even if you "know what you're doing", you may miss this detail. But more importantly, this brings up the issue of how to encode the configuration of the kernel used when a checkpoint is taken. This information would indicate, in a sense, the set of assumptions on the environments that can possibly restart from that checkpoint. This can be checked by user space against the current kernel at restart, and at the very least issue a warning about possible incompatibility. User could override and proceed as is, or modify the image, etc. Coincidentally a similar discussion starts in the other thread on combinations of namespace config options - "[PATCH 1/1] cr: fix compilation with CONFIG_UTS_NS=n", so I'll raise it there. Oren. _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
