All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: mtk.manpages@gmail.com
Cc: Richard Hansen <rhansen@bbn.com>,
	Steven Whitehouse <swhiteho@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Linux API <linux-api@vger.kernel.org>,
	Greg Troxel <gdt@ir.bbn.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC
Date: Thu, 03 Apr 2014 07:51:30 -0400	[thread overview]
Message-ID: <533D4B42.4040600@codeaurora.org> (raw)
In-Reply-To: <CAKgNAki8U+j0mvYCg99j7wJ2Z7ve-gxusVbM3zdog=hKGPdidQ@mail.gmail.com>

On 04/03/2014 04:25 AM, Michael Kerrisk (man-pages) wrote:

> I think the only reasonable solution is to better document existing
> behavior and what the programmer should do. With that in mind, I've
> drafted the following text for the msync(2) man page:
> 
>     NOTES
>        According to POSIX, exactly one of MS_SYNC and MS_ASYNC  must  be
>        specified  in  flags.   However,  Linux permits a call to msync()
>        that specifies neither of these flags, with  semantics  that  are
>        (currently)  equivalent  to  specifying  MS_ASYNC.   (Since Linux
>        2.6.19, MS_ASYNC is in fact a no-op, since  the  kernel  properly
>        tracks  dirty  pages  and  flushes them to storage as necessary.)
>        Notwithstanding the Linux behavior, portable, future-proof appli‐
>        cations  should  ensure  that they specify exactly one of MS_SYNC
>        and MS_ASYNC in flags.

Nit: MS_SYNC or MS_ASYNC

Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

WARNING: multiple messages have this Message-ID (diff)
From: Christopher Covington <cov@codeaurora.org>
To: mtk.manpages@gmail.com
Cc: Richard Hansen <rhansen@bbn.com>,
	Steven Whitehouse <swhiteho@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Linux API <linux-api@vger.kernel.org>,
	Greg Troxel <gdt@ir.bbn.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] mm: msync: require either MS_ASYNC or MS_SYNC
Date: Thu, 03 Apr 2014 07:51:30 -0400	[thread overview]
Message-ID: <533D4B42.4040600@codeaurora.org> (raw)
In-Reply-To: <CAKgNAki8U+j0mvYCg99j7wJ2Z7ve-gxusVbM3zdog=hKGPdidQ@mail.gmail.com>

On 04/03/2014 04:25 AM, Michael Kerrisk (man-pages) wrote:

> I think the only reasonable solution is to better document existing
> behavior and what the programmer should do. With that in mind, I've
> drafted the following text for the msync(2) man page:
> 
>     NOTES
>        According to POSIX, exactly one of MS_SYNC and MS_ASYNC  must  be
>        specified  in  flags.   However,  Linux permits a call to msync()
>        that specifies neither of these flags, with  semantics  that  are
>        (currently)  equivalent  to  specifying  MS_ASYNC.   (Since Linux
>        2.6.19, MS_ASYNC is in fact a no-op, since  the  kernel  properly
>        tracks  dirty  pages  and  flushes them to storage as necessary.)
>        Notwithstanding the Linux behavior, portable, future-proof applia??
>        cations  should  ensure  that they specify exactly one of MS_SYNC
>        and MS_ASYNC in flags.

Nit: MS_SYNC or MS_ASYNC

Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

--
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>

  reply	other threads:[~2014-04-03 11:51 UTC|newest]

Thread overview: 42+ 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 18:25 ` Richard Hansen
     [not found] ` <533B04A9.6090405-A08e6c8yq/Q@public.gmane.org>
2014-04-01 19:32   ` Michael Kerrisk (man-pages)
2014-04-01 19:32     ` Michael Kerrisk (man-pages)
2014-04-01 19:32     ` Michael Kerrisk (man-pages)
2014-04-02  0:53     ` Richard Hansen
2014-04-02  0:53       ` Richard Hansen
     [not found]     ` <533B1439.3010403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-02 10:45       ` chrubis-AlSwsSmVLrQ
2014-04-02 10:45         ` chrubis
2014-04-02 10:45         ` chrubis
2014-04-02 11:10   ` Christoph Hellwig
2014-04-02 11:10     ` Christoph Hellwig
2014-04-02 11:10     ` Christoph Hellwig
     [not found]     ` <20140402111032.GA27551-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-04-02 11:45       ` Steven Whitehouse
2014-04-02 11:45         ` Steven Whitehouse
2014-04-02 11:45         ` Steven Whitehouse
2014-04-02 23:44         ` Richard Hansen
2014-04-02 23:44           ` Richard Hansen
2014-04-02 23:44           ` Richard Hansen
2014-04-03  8:25           ` Michael Kerrisk (man-pages)
2014-04-03  8:25             ` Michael Kerrisk (man-pages)
2014-04-03 11:51             ` Christopher Covington [this message]
2014-04-03 11:51               ` Christopher Covington
2014-04-04  6:54               ` Michael Kerrisk (man-pages)
2014-04-04  6:54                 ` Michael Kerrisk (man-pages)
2014-04-04  6:54                 ` Michael Kerrisk (man-pages)
2014-04-03 12:57             ` Greg Troxel
2014-04-03 12:57               ` Greg Troxel
2014-04-04  7:11               ` Michael Kerrisk (man-pages)
2014-04-04  7:11                 ` Michael Kerrisk (man-pages)
2014-04-04  7:11                 ` Michael Kerrisk (man-pages)
2014-04-03 20:23             ` Richard Hansen
2014-04-03 20:23               ` Richard Hansen
2014-04-04  6:53               ` Christoph Hellwig
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  7:12             ` Michael Kerrisk (man-pages)
2014-04-04  7:12             ` Michael Kerrisk (man-pages)
2014-04-04 14:07             ` Peter Zijlstra
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
2013-09-01 19:58 ` 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=533D4B42.4040600@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=gdt@ir.bbn.com \
    --cc=hch@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rhansen@bbn.com \
    --cc=swhiteho@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.