Revision 78270e8fbc2916bfc8305b8f58f33474cce1ec0e authored by Weston Andros Adamson on 14 August 2014, 21:39:33 UTC, committed by Trond Myklebust on 22 August 2014, 22:04:44 UTC
Commit 6094f83864c1d1296566a282cba05ba613f151ee
"nfs: allow coalescing of subpage requests" got rid of the requirement
that requests cover whole pages, but it made some incorrect assumptions.

It turns out that callers of this interface can map adjacent requests
(by file position as seen by req_offset + req->wb_bytes) to different pages,
even when they could share a page. An example is the direct I/O interface -
iov_iter_get_pages_alloc may return one segment with a partial page filled
and the next segment (which is adjacent in the file position) starts with a
new page.

Reported-by: Toralf Förster <toralf.foerster@gmx.de>
Signed-off-by: Weston Andros Adamson <dros@primarydata.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
1 parent bba5c18
History
File Mode Size
apparmor
integrity
keys
selinux
smack
tomoyo
yama
Kconfig -rw-r--r-- 5.7 KB
Makefile -rw-r--r-- 913 bytes
capability.c -rw-r--r-- 24.6 KB
commoncap.c -rw-r--r-- 28.2 KB
device_cgroup.c -rw-r--r-- 21.1 KB
inode.c -rw-r--r-- 6.7 KB
lsm_audit.c -rw-r--r-- 9.4 KB
min_addr.c -rw-r--r-- 1.3 KB
security.c -rw-r--r-- 36.3 KB

back to top