linux-kernel - Re: [PATCH 00/80] Kernel based checkpoint/restart [v18]

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090926145606.GA30071@elte.hu>
Date:	Sat, 26 Sep 2009 16:56:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dan Smith <danms@...ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Oren Laadan <orenl@...rato.com>, linux-api@...r.kernel.org,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	torvalds@...ux-foundation.org, xemul@...nvz.org
Subject: Re: [PATCH 00/80] Kernel based checkpoint/restart [v18]


* Dan Smith <danms@...ibm.com> wrote:

> >> Q: What additional work needs to be done to it?  A: Fill in the
> >> gory details following the examples so far. Current WIP includes
> >> inet sockets, event-poll, and early work on inotify, mount
> >> namespace and mount-points, pseudo file systems
> 
> AM> Will this new code muck up the kernel, or will it be clean?
> 
> I have (and have previously posted) prototype code to do c/r of open 
> sockets, ignoring some things like updating timers and such.  It looks 
> rather similar to the existing UNIX bits, and is even easier in some 
> ways.
> 
> One particular use case is only migrating listening sockets and 
> allowing the connected ones to be reset upon restart.  That enables a 
> bunch of things like apache, postfix, vncserver, and even sshd.  I 
> will pull the listen-only bits out of my current patch, scrape off a 
> little bitrot, and post them in a few days.

That looks useful. (Btw., the other four questions Andrew asked look 
relevant too.)

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