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: <1219436270.20559.131.camel@nimitz>
Date:	Fri, 22 Aug 2008 13:17:50 -0700
From:	Dave Hansen <dave@...1.net>
To:	Oren Laadan <orenl@...columbia.edu>
Cc:	containers@...ts.linux-foundation.org, jeremy@...p.org,
	linux-kernel@...r.kernel.org, arnd@...db.de
Subject: Re: [RFC v2][PATCH 3/9] x86 support for checkpoint/restart

On Wed, 2008-08-20 at 23:04 -0400, Oren Laadan wrote:+
> +#ifdef CONFIG_X86_64
> +
> +#error "CONFIG_X86_64 unsupported yet."

Well, I told you I'd write some Kconfig magic for you, but I can't since
I can't apply these patches. :)

You need this in a Kconfig file somewhere:

config CHECKPOINT_RESTART
	prompt "Good prompt"
	def_bool y
	depends on X86_32 && EXPERIMENTAL
	help
		Lots of fun help...

config SELECT_ALL_NAMESPACES
	prompt "Enable all kernel namespace support"
	selects IPC_NS NET_NS ...
	help
		This option will save you having to go track down
		all of the individual places that namespaces are
		supported in the kernel.

		If you don't turn this on, the restart porttion
		of checkpoint/restart gets a lots less reliable...	

probably in checkpoint/Kconfig.

Then, in all of the architectures' arch/*/Kconfig files, you need to:

source "checkpoint/Kconfig"

Then, the Makefile looks like this:

--- /dev/null   2008-04-22 10:49:52.000000000 -0700
+++ oren-cr.git-dave/checkpoint/Makefile        2008-08-22 12:30:53.000000000 -0700
@@ -0,0 +1 @@
+obj-$(CONFIG_CHECKPOINT_RESTART) += sys.o checkpoint.o restart.o

-- Dave

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ