Re: [PATCH 5/6] nfs: check all iov segments for correct memory access rights

[Chuck Lever <cel@citi.umich.edu>]

Andrew Morton wrote:
> > +		if (unlikely(!access_ok(type, buf, len))) {
> > +			retval = -EFAULT;
> > +			goto out;
> > +		}
>
> Now what's up here?  Why does NFS, at this level, care about the page's
> virtual address?  get_user_pages() will handle that?

I guess I'm not clear on what behavior is desired for scatter/gather if 
one of the segments in an iov fails.

If one of the iov's will cause an EFAULT, how is that reported back to 
the application, and what happens to the I/O being requested in the 
other segments of the vector?  When do we use an "all or nothing" 
semantic, and when is it OK for some segments to fail?

--
corporate:	cel at netapp dot com
personal:	chucklever at bigfoot dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/