From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Holger Kiehl <Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: NFS write OOPS with 2.6.29.2
Date: Mon, 11 May 2009 08:16:41 -0400 [thread overview]
Message-ID: <1242044201.6691.4.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0905110919490.27423-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
On Mon, 2009-05-11 at 09:24 +0000, Holger Kiehl wrote:
> On Sun, 10 May 2009, Trond Myklebust wrote:
>
> > On Sat, 2009-05-09 at 19:16 +0000, Holger Kiehl wrote:
> >> On Mon, 4 May 2009, Andrew Morton wrote:
> >>
> >>>
> >>> (cc linux-nfs)
> >>>
> >>> On Sun, 3 May 2009 16:03:38 +0000 (GMT) Holger Kiehl <Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org> wrote:
> >>>
> >>>> Hello
> >>>>
> >>>> With plain kernel 2.6.29.2 I get the following OOPS (several of them) when
> >>>> writing lots of small files on the client system:
> >>>>
> >>>> May 3 18:48:34 obelix kernel: ------------[ cut here ]------------
> >>>> May 3 18:48:34 obelix kernel: kernel BUG at fs/nfs/write.c:252!
> >>>
> >>> I think this is a well-know bug, and fixes should be available in 2.6.29.3?
> >>>
> >> Thanks for this information. I just tried 2.6.29.3 and it still oopses.
> >> Are there any patches I can try?
> >
> > The attached backports against 2.6.29 are untested, but they are known
> > to compile at least. Could you give them a try?
> >
> Thanks. They do compile but when there is a mmap on the NFS drive the
> program gets a SIGBUS:
>
> unlink("/home/afdbench/afd2/fifodir/AFD_ACTIVE") = 0
> close(3) = 0
> open("/home/afdbench/afd2/fifodir/AFD_ACTIVE", O_RDWR|O_CREAT|O_TRUNC|O_CLOEXEC, 0600) = 3
> lseek(3, 78, SEEK_SET) = 78
> write(3, "\377"..., 1) = 1
> mmap(NULL, 78, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0x7f8045cdb000
> --- SIGBUS (Bus error) @ 0 (0) ---
>
> This was with 2.6.29.3 plus the patches you send me.
>
> Holger
Oh, duh... You need this little patchlet too.
Sorry...
Cheers
Trond
------------------------------------------------------------------
>From 2b2ec7554cf7ec5e4412f89a5af6abe8ce950700 Mon Sep 17 00:00:00 2001
From: Trond Myklebust <Trond.Myklebust@netapp.com>
Date: Tue, 7 Apr 2009 14:02:53 -0700
Subject: [PATCH] NFS: Fix the return value in nfs_page_mkwrite()
Commit c2ec175c39f62949438354f603f4aa170846aabb ("mm: page_mkwrite
change prototype to match fault") exposed a bug in the NFS
implementation of page_mkwrite. We should be returning 0 on success...
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
---
fs/nfs/file.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nfs/file.c b/fs/nfs/file.c
index 3523b89..5a97bcf 100644
--- a/fs/nfs/file.c
+++ b/fs/nfs/file.c
@@ -516,8 +516,6 @@ static int nfs_vm_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
goto out_unlock;
ret = nfs_updatepage(filp, page, 0, pagelen);
- if (ret == 0)
- ret = pagelen;
out_unlock:
unlock_page(page);
if (ret)
--
1.6.0.4
next prev parent reply other threads:[~2009-05-11 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0905031552340.1774@praktifix.dwd.de>
2009-05-05 6:14 ` NFS write OOPS with 2.6.29.2 Andrew Morton
2009-05-09 19:16 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905091913010.3181-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-10 4:17 ` Trond Myklebust
[not found] ` <1241929074.5149.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 9:24 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905110919490.27423-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-11 12:16 ` Trond Myklebust [this message]
[not found] ` <1242044201.6691.4.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-11 12:45 ` Holger Kiehl
[not found] ` <Pine.LNX.4.64.0905111240190.27423-DdDwMD9x1pcjw5PkpUM3Og@public.gmane.org>
2009-05-11 12:57 ` Trond Myklebust
[not found] ` <1242046675.6691.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-05-13 10:50 ` Suresh Jayaraman
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=1242044201.6691.4.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=Holger.Kiehl-ra7Ruw+Xvfw@public.gmane.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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