squashfs-tools-ng.git/lib, branch v1.0.4

libcommon: backport block processor API update

2021-01-19T10:04:33+00:00

The changes from commit 5191a25b92f903bcc2142be7ea1bfbe5ea1f5096 are backported here in a separate commit since master had some restructuring of libcommon.a after version 1.0.2 and the commit cannot be rebased directly. Signed-off-by: David Oberhollenzer

libsqfs: block processor: backport exact fragment matching

2021-01-19T09:45:59+00:00

This commit is an amalgamation of the commits on master that implement exact matching of fragment blocks during deduplication. Signed-off-by: David Oberhollenzer

libsqfs: implement exact matching in the default block writer.

2021-01-19T09:45:59+00:00

Instead of comparing (compresed, disk-size, checksum) tuples to find block matches, do an exact, byte-for-byte comparison of the data stored on disk to avoid the possibility of a spurious colision. Since this is the desired behaviour, make it the default, optionally overrideable through a flag. Signed-off-by: David Oberhollenzer

Fix: Move fragment consolidation back to block processor serial part

2021-01-19T09:30:20+00:00

Keeping a list of fragments stored away in the current fragment block and consolidating them in the thread pool takes them out of circulation. If we have a lot of tiny fragments, this can lead to a situation where all the limit is reached, but we cannot do anything, because we are waiting for a block to complete, but they are all attached to the current fragment block and the queue is empty. Signed-off-by: David Oberhollenzer

Fix more normalization of slashes in filenames.

2021-01-15T16:36:02+00:00

It looks like the last commit missed a couple more occurences where '\' was treated incorrectly. Fixes were still needed in sqfs_dir_reader_find_by_path and sqfs_dir_reader_get_full_hierarchy. This path is used in extras/browse.c.

Fix normalization of slashes in filenames

2020-12-29T11:39:17+00:00

All paths were canonicalized internally, which includes filtering sequences of slashes and converting backslashes to slashes. Furthermore, when unpacking files, filenames are sanity checked and rejected if they contain forward OR backward slashes. This is a problem on Unix-like systems, where files containing backslashes are a legitimate use case (*cough* SystemD *cough*). This patch removes the backslash conversion from the canonicalization and modifies the sanity check to reject backslashes only on Windows. Signed-off-by: David Oberhollenzer

Fix: libsquashfs: xattr_writer: return NULL if calloc fails

2020-12-29T11:37:37+00:00

Instead of dereferencing the NULL pointer and crashing. Signed-off-by: David Oberhollenzer

Backport changes to builtin copy of zlib

2020-11-02T10:49:44+00:00

Signed-off-by: David Oberhollenzer

Fix integer bounds checking in GNU tar sparse format 1.0 parser

2020-09-03T16:28:09+00:00

- Make sure the file actually has that many records before trying to read one and fail if not. - Use the helper macros for size_t overflow checking instead of assuming size_t == uint64_t. - Impose a "reasonable" upper bound on the number of data segments and insist that there is at least one entry. Signed-off-by: David Oberhollenzer

Fix nonexistant gnu tar sparse format 1.0 support

2020-09-02T09:19:11+00:00

Contrary to previous claims, support for the GNU tar sparse format 1.0 was missing entirely (the newest of their 3 different sparse mapping formats). This oversight wasn't caught, because the unit test was compiling the wrong source file and tar2sqfs had no problem processing the test file because it is still a valid POSIX-ish tar archive (but the sparse part was missing and the mapping embedded in the file). Signed-off-by: David Oberhollenzer