summaryrefslogtreecommitdiff
path: root/include/memory
diff options
context:
space:
mode:
authorJinshan Xiong <jinshan.xiong@intel.com>2016-11-03 04:25:03 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-11-07 13:36:46 +0300
commit7995035f0df50973a15eeb69cfc02446ddacbbbc (patch)
tree8c90ba4c473124a29c7cddb5dc524834ade5e0cb /include/memory
parent4a21aef42fc71e192dc10496e7ce004a3cd986d8 (diff)
downloadlinux-7995035f0df50973a15eeb69cfc02446ddacbbbc.tar.xz
staging/lustre/llite: do not clear uptodate bit in page delete
Otherwise, if the race between page fault and truncate occurs, it will cause the page fault routine to return an EIO error. In filemap_fault() { page_not_uptodate: ... ClearPageError(page); error = mapping->a_ops->readpage(file, page); if (!error) { wait_on_page_locked(page); if (!PageUptodate(page)) error = -EIO; } ... } However, I tend to think this is a defect in kernel implementation, because it assumes PageUptodate shouldn't be cleared but file read routine doesn't make the same assumption. Signed-off-by: Jinshan Xiong <jinshan.xiong@intel.com> Reviewed-on: http://review.whamcloud.com/22827 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8633 Reviewed-by: Li Dongyang <dongyang.li@anu.edu.au> Reviewed-by: Bobi Jam <bobijam@hotmail.com> Signed-off-by: Oleg Drokin <green@linuxhacker.ru> Reviewed-by: James Simmons <jsimmons@infradead.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/memory')
0 files changed, 0 insertions, 0 deletions