| 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: Tue, 21 Oct 2008 13:41:33 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "Serge E. Hallyn" <serue@...ibm.com> Cc: orenl@...columbia.edu, torvalds@...ux-foundation.org, containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, linux-api@...r.kernel.org, tglx@...utronix.de, dave@...ux.vnet.ibm.com, mingo@...e.hu, hpa@...or.com, viro@...iv.linux.org.uk Subject: Re: [RFC v7][PATCH 2/9] General infrastructure for checkpoint restart On Tue, 21 Oct 2008 15:24:10 -0500 "Serge E. Hallyn" <serue@...ibm.com> wrote: > > I'd like to see the security guys take a real close look at all of > > this, and for them to do that effectively they should be provided with > > a full description of the security design of this feature. > > Right, some of the above should be spelled out somewhere. Should it be > in the patch description, in the Documentation/checkpoint.txt file, > or someplace else? Dupliction is usually bad. Documentation/checkpoint.txt would be good (although these things tend to go out of date fast). If you go that way, please ensure that the documentation patch is early in the series and that the changelog says "look in here before whining, dummy". -- 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