From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Richard Hansen <rhansen@bbn.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: mtk.manpages@gmail.com, linux-api@vger.kernel.org,
Greg Troxel <gdt@ir.bbn.com>
Subject: Re: [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC
Date: Tue, 01 Apr 2014 21:32:09 +0200 [thread overview]
Message-ID: <533B1439.3010403@gmail.com> (raw)
In-Reply-To: <533B04A9.6090405@bbn.com>
Richard,
On 04/01/2014 08:25 PM, Richard Hansen wrote:
> For the flags parameter, POSIX says "Either MS_ASYNC or MS_SYNC shall
> be specified, but not both." [1] There was already a test for the
> "both" condition. Add a test to ensure that the caller specified one
> of the flags; fail with EINVAL if neither are specified.
>
> Without this change, specifying neither is the same as specifying
> flags=MS_ASYNC because nothing in msync() is conditioned on the
> MS_ASYNC flag. This has not always been true,
I am curious (since such things should be documented)--when was
it not true?
> 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?
Thanks,
Michael
> [1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/msync.html
>
> Signed-off-by: Richard Hansen <rhansen@bbn.com>
> Reported-by: Greg Troxel <gdt@ir.bbn.com>
> Reviewed-by: Greg Troxel <gdt@ir.bbn.com>
> ---
>
> This is a resend of:
> http://article.gmane.org/gmane.linux.kernel/1554416
> I didn't get any feedback from that submission, so I'm resending it
> without changes.
>
> mm/msync.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/msync.c b/mm/msync.c
> index 632df45..472ad3e 100644
> --- a/mm/msync.c
> +++ b/mm/msync.c
> @@ -42,6 +42,8 @@ SYSCALL_DEFINE3(msync, unsigned long, start, size_t,
> len, int, flags)
> goto out;
> if ((flags & MS_ASYNC) && (flags & MS_SYNC))
> goto out;
> + if (!(flags & (MS_ASYNC | MS_SYNC)))
> + goto out;
> error = -ENOMEM;
> len = (len + ~PAGE_MASK) & PAGE_MASK;
> end = start + len;
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-04-01 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 18:25 [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC Richard Hansen
2014-04-01 19:32 ` Michael Kerrisk (man-pages) [this message]
2014-04-02 0:53 ` Richard Hansen
2014-04-02 10:45 ` chrubis
2014-04-02 11:10 ` Christoph Hellwig
2014-04-02 11:45 ` Steven Whitehouse
2014-04-02 23:44 ` Richard Hansen
2014-04-03 8:25 ` Michael Kerrisk (man-pages)
2014-04-03 11:51 ` Christopher Covington
2014-04-04 6:54 ` Michael Kerrisk (man-pages)
2014-04-03 12:57 ` Greg Troxel
2014-04-04 7:11 ` Michael Kerrisk (man-pages)
2014-04-03 20:23 ` Richard Hansen
2014-04-04 6:53 ` Christoph Hellwig
2014-04-04 7:12 ` [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC [resend] Michael Kerrisk (man-pages)
2014-04-04 14:07 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2013-09-01 19:58 [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC Richard Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533B1439.3010403@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=gdt@ir.bbn.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rhansen@bbn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).