Re: [PATCH 1/1] udf: Fix incorrect final NOT_ALLOCATED (hole) extent length

From: Steve Magnani
Date: Sun Jun 16 2019 - 12:33:43 EST

Hi Jan,

On 6/4/19 7:31 AM, Steve Magnani wrote:

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 shorter than it should be, due to not having
been updated when the file's information length was increased.

Wondering if you've seen this, or if something got lost in a spam folder.


Steven J. Magnani "I claim this network for MARS! Earthling, return my space modulator!"

#include <standard.disclaimer>