Btrfs: read inode size after acquiring the mutex when punching a hole
In a previous change, commit 12870f1c , 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>
parent
7fb18a06
Please register or sign in to comment