Bug#888899: e4defrag: Unsigned integer overflow in failure count when new files created

Control: fixed -1 1.44.6 This does appear to be fixed by https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/misc/e4defrag.c?id=c3749cad154ace57ef3c23a950fbaf44c7ad8a3b I noticed because I tried it on a production 32-bit x86 cache that trivially segfaulted on buster due to the previous fi

Bug#888899: e4defrag: Unsigned integer overflow in failure count when new files created

I just ran e4defrag on an image cache updated to buster, which had had some files cleared and so had space to add new ones. This resulted in following output, demonstrating an invalid failure count close to ULONGLONG_MAX as predicted in #15: # e4defrag -v /cache/ ... [291614/288339]/cache/3e/64d51

Bug#888899: e4defrag: Unsigned integer overflow in failure count when new files created

Package: e2fsprogs Version: 1.43.4-2 Severity: minor I have a web cache which creates and destroys new files on a regular basis. I tried defragmenting the cache folder recently and got this result: # ionice -c3 nice -n 20 e4defrag -v /cache ... [786179/779728]/cache/94/31c16d90eb4dc4d0df8df8