From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: bus errors on nfs writes in latest git
Date: Sat, 04 Apr 2009 12:19:09 -0400 [thread overview]
Message-ID: <1238861949.8114.3.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090404161447.GE495@fieldses.org>
On Sat, 2009-04-04 at 12:14 -0400, J. Bruce Fields wrote:
> My regular connecthon tests are reporting bus errors on the "write/read
> 30 MB file" on recent upstream kernels. I'm travelling and haven't had
> a chance to do anything beyond kick off a dumb git-bisect, which pointed
> the blame at the following commit. Any ideas?
>
> --b.
>
>
> commit c2ec175c39f62949438354f603f4aa170846aabb
> Author: Nick Piggin <npiggin@suse.de>
> Date: Tue Mar 31 15:23:21 2009 -0700
>
> mm: page_mkwrite change prototype to match fault
>
> Change the page_mkwrite prototype to take a struct vm_fault, and return
> VM_FAULT_xxx flags. There should be no functional change.
>
> This makes it possible to return much more detailed error information to
> the VM (and also can provide more information eg. virtual_address to the
> driver, which might be important in some special cases).
>
> This is required for a subsequent fix. And will also make it easier to
> merge page_mkwrite() with fault() in future.
>
> Signed-off-by: Nick Piggin <npiggin@suse.de>
> Cc: Chris Mason <chris.mason@oracle.com>
> Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
> Cc: Miklos Szeredi <miklos@szeredi.hu>
> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Cc: Mark Fasheh <mfasheh@suse.com>
> Cc: Joel Becker <joel.becker@oracle.com>
> Cc: Artem Bityutskiy <dedekind@infradead.org>
> Cc: Felix Blyakher <felixb@sgi.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
<snip>
> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
> index 90f292b..cec7939 100644
> --- a/fs/nfs/file.c
> +++ b/fs/nfs/file.c
> @@ -451,8 +451,9 @@ const struct address_space_operations nfs_file_aops = {
> .launder_page = nfs_launder_page,
> };
>
> -static int nfs_vm_page_mkwrite(struct vm_area_struct *vma, struct page *page)
> +static int nfs_vm_page_mkwrite(struct vm_area_struct *vma, struct vm_fault *vmf)
> {
> + struct page *page = vmf->page;
> struct file *filp = vma->vm_file;
> struct dentry *dentry = filp->f_path.dentry;
> unsigned pagelen;
> @@ -483,6 +484,8 @@ static int nfs_vm_page_mkwrite(struct vm_area_struct *vma, struct page *page)
> ret = pagelen;
^^^^^^^^^^^^^^^^^^
This would explain it. I assume that we're actually supposed to return 0
in case of success.
> out_unlock:
> unlock_page(page);
> + if (ret)
> + ret = VM_FAULT_SIGBUS;
> return ret;
> }
>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2009-04-04 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 16:14 J. Bruce Fields
2009-04-04 16:19 ` Trond Myklebust [this message]
2009-04-04 16:27 ` Trond Myklebust
2009-04-05 20:22 ` J. Bruce Fields
2009-04-06 15:37 ` Geert Uytterhoeven
2009-04-06 6:16 ` 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=1238861949.8114.3.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=npiggin@suse.de \
/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
all inboxes | Powered by JetHome®