linux-kernel - Re: [PATCH 05/10] Core checkpoint/restart support code

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87vcyt4m93.fsf@caffeine.danplanet.com>
Date:	Mon, 04 Apr 2011 16:42:16 -0700
From:	Dan Smith <danms@...ibm.com>
To:	"Serge E. Hallyn" <serge.hallyn@...ntu.com>
Cc:	Nathan Lynch <ntl@...ox.com>,
	containers@...ts.linux-foundation.org,
	Alexey Dobriyan <adobriyan@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 05/10] Core checkpoint/restart support code

SH> The API for starting a checkpoint, that I'm not on the fence on.

Is that just because it requires a C/R aware container init or for some
other reason?  I think the stricter API is a lot easier to understand,
but maybe there's something we can do to avoid that as a hard
requirement?  At least until "C/R support" becomes a desirable feature
of $INIT_DE_JOUR :)

-- 
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/