From: Christoph Hellwig <hch@infradead.org>
To: Richard Hansen <rhansen@bbn.com>
Cc: mtk.manpages@gmail.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, 3 Apr 2014 23:53:53 -0700 [thread overview]
Message-ID: <20140404065353.GA22039@infradead.org> (raw)
In-Reply-To: <533DC357.1080203@bbn.com>
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@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-04 6:54 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)
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 [this message]
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=20140404065353.GA22039@infradead.org \
--to=hch@infradead.org \
--cc=gdt@ir.bbn.com \
--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 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).