Simplify writer code for files without a fragment

The data writer sparse block code can take advantage that it can add a
block size instead of a fragment and doesn't have to initialize the
framgent location.

In return, the tree node to inode serialization code doesn't need a
special case for sparse file anymore and can now also handle files that
are forced to not have a fragment.

Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>

1 files changed, 1 insertions, 7 deletions

diff --git a/lib/sqfs/data_writer.c b/lib/sqfs/data_writer.c
index 8492c98..557b85b 100644
--- a/lib/sqfs/data_writer.c
+++ b/lib/sqfs/data_writer.c
@@ -118,13 +118,7 @@ static int flush_data_block(data_writer_t *data, size_t size, file_info_t *fi)
 	uint32_t out;
 
 	if (is_zero_block(data->block, size)) {
-		if (size < data->super->block_size) {
-			fi->fragment_offset = 0xFFFFFFFF;
-			fi->fragment = 0xFFFFFFFF;
-		} else {
-			fi->blocksizes[data->block_idx++] = 0;
-		}
-
+		fi->blocksizes[data->block_idx++] = 0;
 		fi->sparse += size;
 		return 0;
 	}