| 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: <1193431405.5032.65.camel@localhost> Date: Fri, 26 Oct 2007 16:43:24 -0400 From: Lee Schermerhorn <Lee.Schermerhorn@...com> To: David Rientjes <rientjes@...gle.com> Cc: Paul Jackson <pj@....com>, Christoph Lameter <clameter@....com>, akpm@...ux-foundation.org, ak@...e.de, linux-kernel@...r.kernel.org Subject: Re: [patch 2/2] cpusets: add interleave_over_allowed option On Fri, 2007-10-26 at 11:46 -0700, David Rientjes wrote: > On Fri, 26 Oct 2007, Lee Schermerhorn wrote: > > > Actually, my patch doesn't change the set_mempolicy() API at all, it > > just co-opts a currently unused/illegal value for the nodemask to > > indicate "all allowed nodes". Again, I need to provide a libnuma API to > > request this. Soon come, mon... > > > > If something that was previously unaccepted is now allowed with a > newly-introduced semantic, that's an API change. Well, it's an extension for sure, but a backward compatible one. It should not affect any correct existing application--i.e., one that checks it's return status--except maybe the odd test program that needs to be updated to handle the new semantics. We're allowed to extend APIs as long as we don't break correct applications, right? I mean, it's not like it's a new argument or such. Lee - 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