From: Oleg Nesterov <oleg@tv-sign.ru>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] hugetlbfs private mappings.
Date: Mon, 12 Jul 2004 16:11:18 +0400 [thread overview]
Message-ID: <40F27FE6.A7E4FD96@tv-sign.ru> (raw)
In-Reply-To: 20040712001502.GS21066@holomorphy.com
William Lee Irwin III wrote:
>
> On Sun, Jul 11, 2004 at 04:59:38PM +0400, Oleg Nesterov wrote:
> > Hugetlbfs silently coerce private mappings of hugetlb files
> > into shared ones. So private writable mapping has MAP_SHARED
> > semantics. I think, such mappings should be disallowed.
>
> This probably doesn't break anything worth caring about, but it may
> make people happier to just force MAP_SHARED on.
Yes, it was my initial intent. Andrew Morton pointed out, that
this could break existing applications.
Oleg.
next prev parent reply other threads:[~2004-07-12 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 12:59 [PATCH] hugetlbfs private mappings Oleg Nesterov
2004-07-12 0:15 ` William Lee Irwin III
2004-07-12 12:11 ` Oleg Nesterov [this message]
2004-07-12 19:35 ` William Lee Irwin III
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=40F27FE6.A7E4FD96@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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.