linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andrew Morton <akpm@linux-foundation.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:12:33 +0200	[thread overview]
Message-ID: <20090429071233.GC3398@wotan.suse.de> (raw)
In-Reply-To: <20090428185739.GE6377@localdomain>

On Tue, Apr 28, 2009 at 11:57:39AM -0700, Ravikiran G Thirumalai wrote:
> On Wed, Apr 15, 2009 at 06:38:47PM -0700, Andrew Morton wrote:
> >On Wed, 15 Apr 2009 10:25:07 +0200 Nick Piggin <npiggin@suse.de> wrote:
> >
> >> - Trond for NFS (http://bugzilla.kernel.org/show_bug.cgi?id=12913).
> >
> >I wonder which kernel version(s) we should put this in.
> >
> >Going BUG isn't nice, but that report is against 2.6.27.  Is the BUG
> >super-rare, or did we avoid it via other means, or what?
> >
> 
> Jumping in late in  after being bit by this bug many times
> over with  2.6.27.  The bug (http://bugzilla.kernel.org/show_bug.cgi?id=12913)
> is not rare with the right workload at all.

Good data point, thanks.


> I can easily make it happen on smp machines, when multiple
> processes are writing to the same NFS mounted file system.  AFAICT this
> needs to be back ported to 27 stable and 29 stable as well.
> 
> Nick, are there 27 based patches already available someplace?
> Obviously, I have verified these patches + Trond's patch --
> http://lkml.org/lkml/2009/4/25/64 fixes the issue with 2.6.30-rc3

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.

  reply	other threads:[~2009-04-29  7:12 UTC|newest]

Thread overview: 16+ 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-15  8:25 ` [patch] mm: close page_mkwrite races (try 3) Nick Piggin
2009-04-16  1:38   ` Andrew Morton
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 [this message]
2009-04-29  7:24         ` Andrew Morton
2009-04-29  7:45           ` Nick Piggin
2009-04-29 12:39             ` Trond Myklebust
2009-04-29 15:27               ` Andrew Morton
2009-04-29 16:45                 ` Trond Myklebust
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=20090429071233.GC3398@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 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).