From: Daniel Phillips <phillips@arcor.de>
To: Hugh Dickins <hugh@veritas.com>, "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>, <hch@infradead.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Avoid vmtruncate/mmap-page-fault race
Date: Fri, 23 May 2003 19:10:58 +0200 [thread overview]
Message-ID: <200305231910.58743.phillips@arcor.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305231713230.1602-100000@localhost.localdomain>
On Friday 23 May 2003 18:21, Hugh Dickins wrote:
> Sorry, I miss the point of this patch entirely. At the moment it just
> looks like an unattractive rearrangement - the code churn akpm advised
> against - with no bearing on that vmtruncate race. Please correct me.
This is all about supporting cross-host mmap (nice trick, huh?). Yes,
somebody should post a detailed rfc on that subject.
Regards,
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Phillips <phillips@arcor.de>
To: Hugh Dickins <hugh@veritas.com>, "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
hch@infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Avoid vmtruncate/mmap-page-fault race
Date: Fri, 23 May 2003 19:10:58 +0200 [thread overview]
Message-ID: <200305231910.58743.phillips@arcor.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305231713230.1602-100000@localhost.localdomain>
On Friday 23 May 2003 18:21, Hugh Dickins wrote:
> Sorry, I miss the point of this patch entirely. At the moment it just
> looks like an unattractive rearrangement - the code churn akpm advised
> against - with no bearing on that vmtruncate race. Please correct me.
This is all about supporting cross-host mmap (nice trick, huh?). Yes,
somebody should post a detailed rfc on that subject.
Regards,
Daniel
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-23 16:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 18:21 [RFC][PATCH] vm_operation to avoid pagefault/inval race Daniel Phillips
2003-05-17 18:21 ` Daniel Phillips
2003-05-17 19:49 ` Andrew Morton
2003-05-17 19:49 ` Andrew Morton
2003-05-20 1:23 ` Paul E. McKenney
2003-05-20 1:23 ` Paul E. McKenney
2003-05-20 8:11 ` Andrew Morton
2003-05-20 8:11 ` Andrew Morton
2003-05-23 14:35 ` [RFC][PATCH] Avoid vmtruncate/mmap-page-fault race Paul E. McKenney
2003-05-23 14:35 ` Paul E. McKenney
2003-05-23 16:21 ` Hugh Dickins
2003-05-23 16:21 ` Hugh Dickins
2003-05-23 17:10 ` Daniel Phillips [this message]
2003-05-23 17:10 ` Daniel Phillips
2003-05-23 17:47 ` Hugh Dickins
2003-05-23 17:47 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 18:42 Paul E. McKenney
2003-05-23 18:42 ` Paul E. McKenney
2003-05-29 15:14 ` Paul E. McKenney
2003-05-29 15:14 ` Paul E. McKenney
2003-05-29 16:33 ` Hugh Dickins
2003-05-29 16:33 ` Hugh Dickins
2003-05-29 17:15 ` Daniel Phillips
2003-05-29 17:15 ` Daniel Phillips
2003-05-29 17:39 ` Daniel Phillips
2003-05-29 17:39 ` Daniel Phillips
2003-05-29 20:24 ` Paul E. McKenney
2003-05-29 20:24 ` Paul E. McKenney
2003-05-30 2:38 ` Paul E. McKenney
2003-05-30 2:38 ` Paul E. McKenney
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=200305231910.58743.phillips@arcor.de \
--to=phillips@arcor.de \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@us.ibm.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.