[GFS2] Fix page_mkwrite truncation race path
authorSteven Whitehouse <swhiteho@redhat.com>
Thu, 17 Jan 2008 15:12:03 +0000 (15:12 +0000)
committerSteven Whitehouse <swhiteho@redhat.com>
Fri, 25 Jan 2008 08:20:15 +0000 (08:20 +0000)
commitb7fe2e391ee7b711d6dfd6a694d60c4f21113cbb
tree4a5d141ffd4ae77dc6ce1a47b0bb8ce9d6d7c685
parent3e5cd0877e6d2f059dc36b8206cb7e93938151db
[GFS2] Fix page_mkwrite truncation race path

There was a bug in the truncation/invalidation race path for
->page_mkwrite for gfs2. It ought to return 0 so that the effect is the
same as if the page was truncated at any of the other points at which
the page_lock is dropped. This will result in the restart of the whole
page fault path. If it was due to a real truncation (as opposed to an
invalidate because we let a glock go) then the ->fault path will pick
that up when it gets called again.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/ops_file.c