| 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: <alpine.DEB.2.10.1411241334210.21237@chino.kir.corp.google.com> Date: Mon, 24 Nov 2014 13:34:33 -0800 (PST) From: David Rientjes <rientjes@...gle.com> To: Jianyu Zhan <nasa4836@...il.com> cc: akpm@...ux-foundation.org, mgorman@...e.de, riel@...hat.com, sasha.levin@...cle.com, n-horiguchi@...jp.nec.com, andriy.shevchenko@...ux.intel.com, hannes@...xchg.org, vdavydov@...allels.com, fabf@...net.be, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Jianyu Zhan <jianyu.zhan@....com> Subject: Re: [PATCH] mm, gfp: escalatedly define GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE On Tue, 25 Nov 2014, Jianyu Zhan wrote: > GFP_USER, GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE are escalatedly > confined defined, also implied by their names: > > GFP_USER = GFP_USER > GFP_USER + __GFP_HIGHMEM = GFP_HIGHUSER > GFP_USER + __GFP_HIGHMEM + __GFP_MOVABLE = GFP_HIGHUSER_MOVABLE > > So just make GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE escalatedly defined > to reflect this fact. It also makes the definition clear and texturally > warn on any furture break-up of this escalated relastionship. > > Signed-off-by: Jianyu Zhan <jianyu.zhan@....com> Acked-by: David Rientjes <rientjes@...gle.com> -- 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