From: Nick Piggin <npiggin-l3A5Bk7waGM@public.gmane.org>
To: Trond Myklebust
<trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Rince <rincebrain-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NFS BUG_ON in nfs_do_writepage
Date: Sun, 26 Apr 2009 08:40:26 +0200 [thread overview]
Message-ID: <20090426064026.GD28555@wotan.suse.de> (raw)
In-Reply-To: <1240671428.6112.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Sat, Apr 25, 2009 at 10:57:08AM -0400, Trond Myklebust wrote:
> On Fri, 2009-04-24 at 05:26 -0400, Rince wrote:
> > Applied try 3 of Nick Piggin's patch to 2.6.30-rc3 (cleanly, no less!)
> >
> > Doesn't appear to have helped at all - I received my favorite BUG ON
> > write.c:252 just like always, within 24 hours of booting the kernel,
> > even.
>
> Can you apply the following incremental patch on top of Nick's. This
> appears to suffice to close the race on my setup.
Thanks, yes that looks good. Note: I deliberately didn't try to
convert filesystems because it needs much better understanding
of each one. So any fs maintainers using page_mkwrite I hope have
looked at these patches and considered whether they need to
do anything differently (ditto for the page_mkwrite return value
fixup patch).
Thanks,
Nick
>
> Cheers
> Trond
> ---------------------------------------------------------------------
> >From f0258852dcb43c748854d2ee550c9c270bb25f21 Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
> Date: Fri, 24 Apr 2009 17:32:22 -0400
> Subject: [PATCH] NFS: Close page_mkwrite() races
>
> Follow up to Nick Piggin's patches to ensure that nfs_vm_page_mkwrite
> returns with the page lock held, and sets the VM_FAULT_LOCKED flag.
>
> Signed-off-by: Trond Myklebust <Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
> ---
> fs/nfs/file.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
> index 5a97bcf..ec7e27d 100644
> --- a/fs/nfs/file.c
> +++ b/fs/nfs/file.c
> @@ -517,10 +517,10 @@ static int nfs_vm_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
>
> ret = nfs_updatepage(filp, page, 0, pagelen);
> out_unlock:
> + if (!ret)
> + return VM_FAULT_LOCKED;
> unlock_page(page);
> - if (ret)
> - ret = VM_FAULT_SIGBUS;
> - return ret;
> + return VM_FAULT_SIGBUS;
> }
>
> static struct vm_operations_struct nfs_file_vm_ops = {
> --
> 1.6.0.6
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2009-04-26 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0904130145050.4396@centaur.acm.jhu.edu>
[not found] ` <20090412235010.c8e3475b.akpm@linux-foundation.org>
[not found] ` <1239650202.16771.15.camel@heimdal.trondhjem.org>
[not found] ` <5da0588e0904131506k5c58e8ddob9bf38f61da6302a@mail.gmail.com>
[not found] ` <5da0588e0904131644g131dc816r61884e83bc4cd006@mail.gmail.com>
[not found] ` <5da0588e0904240226j3454941y5f58c17a32a9a23d@mail.gmail.com>
[not found] ` <1240671428.6112.1.camel@heimdal.trondhjem.org>
[not found] ` <1240671428.6112.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-26 6:40 ` Nick Piggin [this message]
2009-04-26 14:18 ` NFS BUG_ON in nfs_do_writepage Trond Myklebust
2009-04-26 15:13 ` Nick Piggin
2009-04-26 17:55 ` Trond Myklebust
[not found] ` <1240768522.10548.33.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-04-28 4:27 ` Nick Piggin
[not found] ` <20090428042717.GA6304-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2009-04-28 11:45 ` Trond Myklebust
2009-04-28 11:54 ` Nick Piggin
2009-04-28 11:59 ` 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=20090426064026.GD28555@wotan.suse.de \
--to=npiggin-l3a5bk7wagm@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rincebrain-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).