Messages in this thread | | | Date | Wed, 2 Apr 2014 12:45:17 +0200 | From | chrubis@suse ... | Subject | Re: [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC |
| |
Hi! > > and there's no good > > reason to believe that this behavior would have persisted > > indefinitely. > > > > The msync(2) man page (as currently written in man-pages.git) is > > silent on the behavior if both flags are unset, so this change should > > not break an application written by somone who carefully reads the > > Linux man pages or the POSIX spec. > > Sadly, people do not always carefully read man pages, so there > remains the chance that a change like this will break applications. > Aside from standards conformance, what do you see as the benefit > of the change?
I've looked around Linux Test Project and this change will break a few testcases, but nothing that couldn't be easily fixed.
The rest of the world may be more problematic though.
-- Cyril Hrubis chrubis@suse.cz
| |