| 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: <20080305101015.cdff44f2.akpm@linux-foundation.org> Date: Wed, 5 Mar 2008 10:10:15 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Paul Jackson <pj@....com> Cc: menage@...gle.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH 0/2] Cpuset hardwall flag: Introduction On Wed, 5 Mar 2008 06:23:18 -0600 Paul Jackson <pj@....com> wrote: > Paul M wrote: > > Currently the cpusets mem_exclusive flag is overloaded to mean both > > "no-overlapping" and "no GFP_KERNEL allocations outside this cpuset". > > > > These patches add a new mem_hardwall flag with just the allocation > > restriction part of the mem_exclusive semantics, without breaking > > backwards-compatibility for those who continue to use just > > mem_exclusive. > > ... too bad this nice comment wasn't included in PATCH 2/2, so that > it would automatically make it into the record of history - the source > control log message (as best I understand how Andrew's tools work, > comments off in their own, codeless patch "PATCH 0/N" don't make > it to the source control log, except when Andrew chooses to make a > special effort.) I make that special effort almost 100% of the time. The changelog for the first patch becomes: <text from [0/n]> This patch: <text from [1/n]> -- 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