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, 8 Jan 2008 14:01:11 +1100 From: Nick Piggin <nickpiggin@...oo.com.au> To: David Howells <dhowells@...hat.com> Cc: viro@....linux.org.uk, hch@...radead.org, Trond.Myklebust@...app.com, sds@...ho.nsa.gov, casey@...aufler-ca.com, linux-kernel@...r.kernel.org, selinux@...ho.nsa.gov, linux-security-module@...r.kernel.org Subject: Re: [PATCH 10/28] FS-Cache: Recruit a couple of page flags for cache management [try #2] On Tuesday 08 January 2008 00:09, David Howells wrote: > Nick Piggin <nickpiggin@...oo.com.au> wrote: > > No. I mean call the bit PG_private2. That way non-pagecache and > > filesystems that don't use fscache can use it. > > The bit is called PG_owner_priv_2, and then 'subclassed' to PG_fscache, > much like PG_owner_priv_1 is 'subclassed' to PG_checked as was recommended. It is not owner_priv if you're putting checks and tests into core kernel pagecache code for it. owner_priv means a filesystem has it _all_ to itself. -- 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