squashfs-tools-ng.git/lib/sqfs/block_processor, branch master

Move library source into src sub-directory

2023-01-31T12:51:49+00:00

Signed-off-by: David Oberhollenzer

Implement rudimentary reference counting for sqfs_object_t

2023-01-19T15:24:56+00:00

Implement grab/drop functions to increase/decrease reference count and destroy the object if the count drops to 0. Make sure that all objects that maintain internal references actually grab that reference, duplicate it in the copy function, drop it in the destroy handler. Signed-off-by: David Oberhollenzer

Add a helper function to initialize libsquashfs objects

2023-01-19T15:24:56+00:00

Signed-off-by: David Oberhollenzer

libsqfs: Fix an overzealous bounds check in the block processor

2022-11-18T15:21:12+00:00

When (during fragment deduplication) a fragment block is read back from disk and unpacked, it can happen that it is _exactly_ the given block size. The bounds check did '>=' instead of '>' and failed in that case with a "data corruption" error. Signed-off-by: David Oberhollenzer

Cleanup: move libutil headers to sub directory

2022-07-08T17:17:35+00:00

Move all the libutil stuff from the toplevel include/ to a util/ sub directory and fix up the includes that make use of them. Signed-off-by: David Oberhollenzer

libsquashfs: fix: also preserve alignment flag in block processor

2021-06-07T09:28:47+00:00

Currently, when the block processor aggreagtes fragments into a fragment block, it applies the "don't compress" flag if any of the original framgnets has it set, but the "align to device block" flag is lost. This commit ensures that both flags get applied to the fragment block if set. Signed-off-by: David Oberhollenzer

libsqfs: block processor: Fix account for manually submitted blocks

2021-03-30T10:42:43+00:00

This was already in the original block processor but got dropped by accident when restructuring it. The problem manifests itself when manually submitting fragment blocks. They no longer get correct I/O queue tickets, clog up the queue and the processor eventually throws an internal error. Signed-off-by: David Oberhollenzer

Fix fail branch in block processor fragment backend

2021-03-25T13:47:06+00:00

Only clean up the fragment if it hasn't been re-assigned to the fragment block. The NULL check is definitely wrong, because we no longer re-assign it as NULL. Signed-off-by: David Oberhollenzer

Fix block processor queue accounting

2021-03-24T13:05:18+00:00

Dequeuing won't work if we have a backlog of 1 or 2 and the blocks are used for internal buffering. Take that into account, similar to the sync code. Also bump the minimum backlog to 3, just to make absolutely sure we cannot run into a dequeue loop trying to allocate a block. Signed-off-by: David Oberhollenzer

block processor: Re-implement exact fragment matching

2021-03-23T10:39:52+00:00

In the hash-table equals callback, if the hash and size match, do an exact, byte-for-byte comparison of the fragment in question. The fragment can either be in a fragment block that is in-flight (for which we have the in-flight list), in the current, unfinished fragment block, or it can be on disk. In the later case, the fragment block is resolved through the fragment table and read back from disk into a scratch buffer and decompressed. After that, the fragment is checked for byte-for-byte equality with the one we resolved through the hash table. Signed-off-by: David Oberhollenzer