All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
	Sage Weil <sage@newdream.net>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-fsdevel@vger.kernel.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] mm: close page_mkwrite races (try 3)
Date: Wed, 29 Apr 2009 09:45:11 +0200	[thread overview]
Message-ID: <20090429074511.GD3398@wotan.suse.de> (raw)
In-Reply-To: <20090429002418.fd9072a6.akpm@linux-foundation.org>

On Wed, Apr 29, 2009 at 12:24:18AM -0700, Andrew Morton wrote:
> On Wed, 29 Apr 2009 09:12:33 +0200 Nick Piggin <npiggin@suse.de> wrote:
> 
> > I haven't got any prepared, but they should be a pretty trivial
> > backport, provided we also backport c2ec175c39f62949438354f603f4aa170846aabb
> > (which is probably a good idea anyway).
> > 
> > However I will probably wait for a bit, given that the patch isn't upstream
> > yet.
> 
> err, I'd marked it as for-2.6.31.  It looks like that was wrong?

At the time I agreed because I didn't know the severity of the NFS
bugs. So it is up to you and Trond / nfs guys I guess.


> all this:
> 
> #mm-close-page_mkwrite-races-try-3.patch: akpm issues!
> #mm-close-page_mkwrite-races-try-3.patch: check akpm hack
> mm-close-page_mkwrite-races-try-3.patch
> mm-close-page_mkwrite-races-try-3-update.patch
> mm-close-page_mkwrite-races-try-3-fix.patch
> mm-close-page_mkwrite-races-try-3-fix-fix.patch
> 
> is a bit of a worry.  But I guess we won't know until we merge it.

I have nothing against merging it now if you think it is needed.
It's only adding synchronisation, so I doubt it will cause a problem
that pushes the release out.

--
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:[~2009-04-29  7:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  7:11 [patch] mm: close page_mkwrite races (try 2) Nick Piggin
2009-04-14  7:11 ` Nick Piggin
2009-04-15  8:25 ` [patch] mm: close page_mkwrite races (try 3) Nick Piggin
2009-04-15  8:25   ` Nick Piggin
2009-04-16  1:38   ` Andrew Morton
2009-04-16  2:03     ` Nick Piggin
2009-04-16  2:03       ` Nick Piggin
2009-04-16  2:23     ` Nick Piggin
2009-04-28 18:57     ` Ravikiran G Thirumalai
2009-04-29  7:12       ` Nick Piggin
2009-04-29  7:12         ` Nick Piggin
2009-04-29  7:24         ` Andrew Morton
2009-04-29  7:45           ` Nick Piggin [this message]
2009-04-29 12:39             ` Trond Myklebust
2009-04-29 15:27               ` Andrew Morton
2009-04-29 16:45                 ` Trond Myklebust
2009-04-29 16:45                   ` Trond Myklebust
2009-04-30 14:22                   ` Rince
2009-04-30 14:22                     ` Rince
2009-04-30 14:33                     ` Rince
2009-05-02 22:12                       ` Rince
2009-05-03  1:38                         ` Trond Myklebust

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=20090429074511.GD3398@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=kiran@scalex86.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sage@newdream.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.