mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: David Howells <dhowells@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: what happened to page_mkwrite? - was: Re: page_mkwrite seems broken
Date: Mon, 24 Oct 2005 16:36:26 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0510241625230.4112@goblin.wat.veritas.com> (raw)
In-Reply-To: <1130167005.19518.35.camel@imp.csi.cam.ac.uk>

On Mon, 24 Oct 2005, Anton Altaparmakov wrote:
> On Wed, 2005-02-09 at 14:28 +0000, Hugh Dickins wrote:
> > On Fri, 4 Feb 2005, Hugh Dickins wrote in another thread:
> > > Isn't this exactly what David Howells' page_mkwrite stuff in -mm's
> > > add-page-becoming-writable-notification.patch is designed for?
> > > 
> > > Though it looks a little broken to me as it stands (beyond the two
> > > fixup patches already there).  I've not found time to double-check
.....
> 
> What happened with page_mkwrite?  It seems to have disappeared both from
> -mm and generally from the face of the earth...

page_mkwrite??  No, never heard of it round here, you must be mistaken ;)

But seriously, Andrew dropped it from 2.6.13-rc5-mm1, for expedient reasons:
- Dropped cachefs and the cachefs-for-AFS patches.  These get in the way of
  memory management testing a bit, and they're being redone anyway.

So Andrew's 2.6.13-rc4-mm1 directory should contain its last public state
(by which time I'd fixed up those various things I'd found to be broken).

But David may have redone a lot since then, I don't know: he's the one
to ask.  (And I'm afraid I've done my best to make the old patch not
apply to current -mm.)

Hugh

> I am very interested in having such ability for ntfs...
> 
> Is anyone still working on this?  If not why not?  Did it prove
> impractical or ...?
> 
> If no-one is working on this anymore, where do I find the last "current"
> patch?
> 
> Thanks a lot in advance!
> 
> Best regards,
> 
>         Anton

  reply	other threads:[~2005-10-24 15:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 14:28 Hugh Dickins
2005-10-24 15:16 ` what happened to page_mkwrite? - was: " Anton Altaparmakov
2005-10-24 15:36   ` Hugh Dickins [this message]
2005-10-24 15:49     ` Anton Altaparmakov
2005-10-24 15:26 ` David Howells
2005-10-24 15:43   ` Anton Altaparmakov
2005-10-24 16:01     ` Hugh Dickins
2005-10-24 19:38       ` Anton Altaparmakov
2005-10-24 20:31         ` Hugh Dickins
2005-10-24 21:18           ` Anton Altaparmakov
2005-10-24 16:23   ` [PATCH] Add notification of page becoming writable to VMA ops David Howells
2005-10-24 19:11     ` Hugh Dickins
2005-10-25  7:59       ` Anton Altaparmakov
2005-10-25  8:26         ` Hugh Dickins
2005-10-25  8:49           ` Anton Altaparmakov
2005-10-25  9:49     ` David Howells
2005-10-25  9:55     ` David Howells
2005-10-25 10:12     ` David Howells
2005-10-25 13:18     ` [PATCH] Add notification of page becoming writable to VMA ops [try #2] David Howells
2005-11-30 13:58     ` [PATCH] Add notification of page becoming writable to VMA ops [try #3] David Howells
2005-11-30 14:40       ` Miklos Szeredi
2005-11-30 14:50       ` David Howells
2005-11-30 15:20     ` [PATCH] Add notification of page becoming writable to VMA ops [try #4] David Howells
2006-01-11 12:19     ` [PATCH] Add notification of page becoming writable to VMA ops [try #5] 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=Pine.LNX.4.61.0510241625230.4112@goblin.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®