linux-kernel - Re: bus errors on nfs writes in latest git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 04 Apr 2009 12:19:09 -0400
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	linux-nfs@...r.kernel.org, Nick Piggin <npiggin@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: bus errors on nfs writes in latest git

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@...e.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@...e.de>
>     Cc: Chris Mason <chris.mason@...cle.com>
>     Cc: Trond Myklebust <trond.myklebust@....uio.no>
>     Cc: Miklos Szeredi <miklos@...redi.hu>
>     Cc: Steven Whitehouse <swhiteho@...hat.com>
>     Cc: Mark Fasheh <mfasheh@...e.com>
>     Cc: Joel Becker <joel.becker@...cle.com>
>     Cc: Artem Bityutskiy <dedekind@...radead.org>
>     Cc: Felix Blyakher <felixb@....com>
>     Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
>     Signed-off-by: Linus Torvalds <torvalds@...ux-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@...app.com
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/