| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 30 Sep 2009 09:29:23 -0700 From: Dan Smith <danms@...ibm.com> To: Daniel Lezcano <daniel.lezcano@...e.fr> Cc: "Serge E. Hallyn" <serue@...ibm.com>, linux-api@...r.kernel.org, containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, torvalds@...ux-foundation.org, mingo@...e.hu, xemul@...nvz.org Subject: Re: [PATCH 00/80] Kernel based checkpoint/restart [v18] DL> If the checkpoint is done from the kernel, why the restart DL> wouldn't be in the kernel too ? I think thus far we have taken the approach of "if it can be done reasonably in userspace, then do it there" right? Setup of the network devices is easy to do in userspace, allows more flexibility from a policy standpoint, and ensures that all existing security checks are performed. Also, migration may be easier if the userspace bits can call custom hooks allowing for routing changes and other infrastructure-specific operations. DL> Is there any documentation about the statefile format I can use if DL> I want to implement myself an userspace CR solution based on this DL> kernel patchset ? See linux-cr/include/linux/checkpoint_hdr.h and user-cr/restart.c. -- Dan Smith IBM Linux Technology Center email: danms@...ibm.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists