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, 20 Feb 2013 14:51:09 +0400 From: Cyrill Gorcunov <gorcunov@...nvz.org> To: Amnon Shiloh <u3557@...o.sublimeip.com> Cc: Steven Rostedt <rostedt@...dmis.org>, u3557@...lix.com.au, Oleg Nesterov <oleg@...hat.com>, Pedro Alves <palves@...hat.com>, Denys Vlasenko <dvlasenk@...hat.com>, Jan Kratochvil <jan.kratochvil@...hat.com>, Pavel Emelyanov <xemul@...allels.com>, Frederic Weisbecker <fweisbec@...il.com>, Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-kernel@...r.kernel.org Subject: Re: prctl(PR_SET_MM) On Wed, Feb 20, 2013 at 08:38:01PM +1100, Amnon Shiloh wrote: > > I personally don't mind if this come become y by default, because it will > > work for us. > > I don't mind either, to say the least, to have CONFIG_CHECKPOINT_RESTORE > have a "default y" in "init/Kconfig" - that would solve my problem and make > me happy, as well as your group and others, but we are told here that Linus > has a policy vetoing such changes and I don't believe either of us can make > him change his mind. That's perfectly fine for all new features :-) > As such, we must look at other options, such as having the code in > "kernel/sys.c" out in the open, not enclosed by any #ifdef's altogether > - surely you would like that! > > > Still I guess if you need to reconstruct Linux process(es) > > plain prctl extension is not enough, you still need a functionality which > > is enclosed in config-checkpoint-restore (say /proc/pid/map_files, kcmp), > > no? > > My process-migration package only reconstructs Linux processes partially: > as it's a bit different than any classical checkpoint-restore, the critical > code in "kernel/sys.c" is all I need at the moment (from within > CONFIG_CHECKPOINT_RESTORE). I do appreciate that anyone attempting to > perform complete, classical, checkpoint-restore operations, needs more > than that. I see. Thanks for explanation! Thus we need some new config option which would enable this prctl opcodes (y by default), in turn config-checkpoint-restore kconfig option need to select this feature if set. Sounds reasonable? -- 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