udf: Fix incorrect final NOT_ALLOCATED (hole) extent length
authorSteven J. Magnani <steve.magnani@digidescorp.com>
Mon, 1 Jul 2019 02:39:35 +0000 (21:39 -0500)
committerJan Kara <jack@suse.cz>
Wed, 10 Jul 2019 08:11:24 +0000 (10:11 +0200)
commitfa33cdbf3eceb0206a4f844fe91aeebcf6ff2b7a
tree281cbca1317d602a0d7cbabf37b7e492cc5be3ec
parent90f15ac9fa7e7ff66e0980309d8184bff0611624
udf: Fix incorrect final NOT_ALLOCATED (hole) extent length

In some cases, using the 'truncate' command to extend a UDF file results
in a mismatch between the length of the file's extents (specifically, due
to incorrect length of the final NOT_ALLOCATED extent) and the information
(file) length. The discrepancy can prevent other operating systems
(i.e., Windows 10) from opening the file.

Two particular errors have been observed when extending a file:

1. The final extent is larger than it should be, having been rounded up
   to a multiple of the block size.

B. The final extent is not shorter than it should be, due to not having
   been updated when the file's information length was increased.

[JK: simplified udf_do_extend_final_block(), fixed up some types]

Fixes: 2c948b3f86e5 ("udf: Avoid IO in udf_clear_inode")
CC: stable@vger.kernel.org
Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
Link: https://lore.kernel.org/r/1561948775-5878-1-git-send-email-steve@digidescorp.com
Signed-off-by: Jan Kara <jack@suse.cz>
fs/udf/inode.c