| 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
| ||
|
Message-Id: <1235438459.26788.222.camel@nimitz> Date: Mon, 23 Feb 2009 17:20:59 -0800 From: Dave Hansen <dave@...ux.vnet.ibm.com> To: "Serge E. Hallyn" <serue@...ibm.com> Cc: containers <containers@...ts.linux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Alexey Dobriyan <adobriyan@...il.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [RFC][PATCH 3/5] check files for checkpointability On Mon, 2009-02-23 at 19:10 -0600, Serge E. Hallyn wrote: > > This allows us to tell where and when we went wrong. Take a process > > that's been running for a month. After 5 days it did something random > > to keep it from being checkpointed. You're going to have forgotten all > > about it 25 days later. This gives us an opportunity to spit into dmesg > > or just plain log it. It also gives the app some ability to reflect and > > see what its uncheckpointable attributes are. > > Hmm. In that case, rather than refuse checkpoint, I prefer that we make > this a footnote in the /proc/$$/checkpointable output. Yeah, that's cool. If we were smart, we'd also get hooked into some of the ftrace output so that we have a real chance of logging these things and being able to go look at something about them down the line. -- 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