Guys, I don't really see why you get so worked up about this. There is lots and lots of precedent of Linux allowing non-Posix (or non-standard in general) arguments to system calls. Even ones that don't have symbolic names defined for them (the magic 3 open argument for device files). Given that we historicaly allowed the 0 argument to msync we'll have to keep supporting it to not break existing userspace, and adding warnings triggered by userspace that the person running the system usually can't fix for something that is entirely harmless at runtime isn't going to win you friends either. A "strictly Posix" environment that catches all this sounds fine to me, but it's something that should in the userspace c runtime, not the kernel. The kernel has never been about strict Posix implementations, it sometimes doesn't even make it easy to implement the semantics in user land, which is a bit unfortunate. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>