| 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: <20090219190009.GC28490@infradead.org> Date: Thu, 19 Feb 2009 14:00:09 -0500 From: Christoph Hellwig <hch@...radead.org> To: Dave Hansen <dave@...ux.vnet.ibm.com> Cc: Ingo Molnar <mingo@...e.hu>, containers <containers@...ts.linux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Serge E. Hallyn" <serue@...ibm.com>, Oren Laadan <orenl@...columbia.edu>, Alexey Dobriyan <adobriyan@...il.com> Subject: Re: [RFC][PATCH 1/5] create fs flag to mark c/r supported fs's On Thu, Feb 19, 2009 at 10:20:07AM -0800, Dave Hansen wrote: > > There are plenty of filesystems that are not supported for > c/r at this point. Think of things like hugetlbfs which > are externally visible or pipefs which are kernel-internal. > > This provides a quick way to make the "normal" filesystems > which are currently supported. This is also safe if any > new code gets added. We assume that a fs is non-supported > unless someone takes explicit action to the contrary. > > I bet there are some more filesystems that are OK, but > these probably cover 99% of the users for now. Given that a normal fs should be checkpointable you should make those exposing internal state, not the other way around. -- 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