linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: David Chinner <dgc@sgi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	randy.dunlap@oracle.com
Subject: Re: [patch 2/8] mm: merge populate and nopage into fault (fixes nonlinear)
Date: Wed, 23 May 2007 11:35:40 +0200	[thread overview]
Message-ID: <20070523093540.GA22453@wotan.suse.de> (raw)
In-Reply-To: <20070523083548.GX86004887@sgi.com>

On Wed, May 23, 2007 at 06:35:48PM +1000, David Chinner wrote:
> On Tue, May 22, 2007 at 06:14:47PM -0700, Linus Torvalds wrote:
> > 
> > 
> > On Tue, 22 May 2007, Christoph Hellwig wrote:
> > >
> > > On Fri, May 18, 2007 at 08:11:35AM -0700, Linus Torvalds wrote:
> > > > 
> > > > On Fri, 18 May 2007, akpm@linux-foundation.org wrote:
> > > > > 
> > > > > Nonlinear mappings are (AFAIKS) simply a virtual memory concept that encodes
> > > > > the virtual address -> file offset differently from linear mappings.
> > > > 
> > > > I'm not going to merge this one.
> > > 
> > > So if ->fault doesn't get in can be please at least get block_page_mkwrite
> > > in to fix the shared mmap write allocation and unwritten extent + mmap
> > > issues?  It can then later be converted to whatever version of ->fault
> > > goes in.
> > 
> > After a -rc2? 
> > 
> > I don't think so. Unless it's some new regression.
> 
> It's an old bug that ppl have been asking to be fixed for
> a long time. I fixed it a couple of months back, only to have
> inclusion put on hold because a) there was nothing XFS sepcific
> and it should be made generic, and b) the generic implementation
> conflicted with the impending ->fault work and hence was held back.
> 
> If neither of these things occurred, the XFS specific fix would have
> been released in 2.6.21. As it stands, the only user of
> block_page_mkwrite() would be XFS for 2.6.22 and the patches have
> been sitting in my QA tree for a couple of months now just waiting
> to go somewhere....
> 
> What's the plan for ->fault moving forward?

I don't see why it couldn't go into 2.6.23 (at the start of the merge
window, next time, would be preferable).

But don't let the ->fault work hold you up. You should even be able to
get it into -mm, because I haven't got the ->page_mkwrite conversion in
there yet.

--
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>

  reply	other threads:[~2007-05-23  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  7:37 akpm, Nick Piggin
2007-05-18 10:24 ` Christoph Hellwig
2007-05-18 15:11 ` Linus Torvalds
2007-05-19  1:38   ` Nick Piggin
2007-05-22 15:12   ` Christoph Hellwig
2007-05-23  1:14     ` Linus Torvalds
2007-05-23  8:35       ` David Chinner
2007-05-23  9:35         ` Nick Piggin [this message]
2007-05-23  2:57     ` Nick Piggin
2007-05-23 23:37   ` Benjamin Herrenschmidt
2007-05-24  1:48     ` Nick Piggin
2007-05-24  2:06       ` Linus Torvalds
2007-05-24  2:24         ` Nick Piggin

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=20070523093540.GA22453@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.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