From: Filipe Manana <fdmanana@gmail.com>
Date: Sat, 26 Apr 2014 00:35:31 +0000 (+0100)
Subject: Btrfs: read inode size after acquiring the mutex when punching a hole
X-Git-Tag: omap-for-v3.16/fixes-against-rc1~54^2~73
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a1a50f60a6bf4f861eb94793420274bc1ccd409a;p=pandora-kernel.git

Btrfs: read inode size after acquiring the mutex when punching a hole

In a previous change, commit 12870f1c9b2de7d475d22e73fd7db1b418599725,
I accidentally moved the roundup of inode->i_size to outside of the
critical section delimited by the inode mutex, which is not atomic and
not correct since the size can be changed by other task before we acquire
the mutex. Therefore fix it.

Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
Signed-off-by: Chris Mason <clm@fb.com>
---

Reading git-diff-tree failed