From: Andrew Morton <akpm@osdl.org>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [-mm PATCH] ocfs2: Shared writeable mmap
Date: Mon, 19 Jun 2006 17:07:36 -0700 [thread overview]
Message-ID: <20060619170736.65237ce7.akpm@osdl.org> (raw)
In-Reply-To: <20060619234643.GK3082@ca-server1.us.oracle.com>
Mark Fasheh <mark.fasheh@oracle.com> wrote:
>
> I finally got some time to sit down and implement an OCFS2 patch to make use
> of the ->page_mkwrite() callback added by David Howells' patch (named
> 'add-page_mkwrite-vm_operations-method.patch' in -mm). The patches, and an
> MPI program to test this can be found at:
>
> http://kernel.org/pub/linux/kernel/people/mfasheh/ocfs2/mmap/
>
> There's one bug however, which will cause the test program on one of the
> reading nodes to see stale data if it is run several times in a row against
> the same file. I have verified that the same thing works fine on a local
> file system (ext3). I'm not sure where the issue is, but I have a feeling
> I'm doing something bad in ocfs2_data_convert_worker(). Another possibility
> is that we missed a place to put the ->page_mkwrite callback.
>
> Unfortunately, I have to step away from this patch for a bit as I have some
> higher priority issues to deal with :/ Luckily, it seems to be in a state
> which I think warrants it being pushed out to the public for general review,
> testing, etc. If anyone is interested, I'd also appreciate any advice or
> help regarding the bug -- my VM-foo is very weak :)
Peter Zijlstra told me yesterday:
There is a problem with the page-mkwrite last posted to lkml. /me
checks your tree... Yeah, that version has a problem:
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm2/broken-out/add-page_mkwrite-vm_operations-method.patch
The thing is that get_user_pages(.write=1, .force=1) can generate COW
hits on read-only shared mappings, this patch traps those as mkpage_write
candidates and fails to handle them the old way.
Which I was unaware of and haven't started to think about. Probably I'll
drop the existing patch and pick up the one he's sending out. But it's
presumably based on top of all the dirty-page-tracking patches which I also
haven't thought about yet and which need _serious_ thought.
It would be better to get a fix against the existing
add-page_mkwrite-vm_operations-method.patch so at least we can get that
merged up. But nobody seems to be offering that.
next prev parent reply other threads:[~2006-06-20 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 23:46 [-mm PATCH] ocfs2: Shared writeable mmap Mark Fasheh
2006-06-19 23:55 ` [Ocfs2-devel] " Daniel Phillips
2006-06-20 5:42 ` Mark Fasheh
2006-06-20 0:07 ` Andrew Morton [this message]
2006-06-20 0:52 ` Mark Fasheh
2006-06-20 7:07 ` Peter Zijlstra
2006-06-20 12:59 ` David Howells
2006-06-20 13:02 ` David Howells
2006-06-20 13:20 ` [PATCH] Add notification of page becoming writable to VMA ops David Howells
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=20060619170736.65237ce7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).