Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
fix_ldconfig.patch | no | |||||
05_libreiser4~profile.c.patch | no | |||||
Build-with-libedit-instead-of-readline.patch | Build with libedit instead of readline | Bastian Germann <bastiangermann@fishpost.de> | no | 2020-07-23 | ||
fix_print_uuid.patch | Fix up repair_master_print() Use the right criteria to make sure that uuid is set diff --git a/librepair/master.c b/librepair/master.c index c7806c566..dadf21a3c 100644 |
Edward Shishkin <edward.shishkin@gmail.com> | no | debian | upstream, https://github.com/edward6/reiser4progs/commit/4802cdb18ae03031d0e51a58b6655f3b99021ec2 | 2021-03-13 |
fix_null_uuid.patch | Stop occasionally making file systems with null UUIDs mkfs.reiser4 was using strncpy() to copy a binary UUID into the in-memory copy of the superblock. So if there was a zero byte in the UUID, then from that point to the end was set to all zeros. If the first byte was zero, a 1 in 256 chance, then the whole UUID was set to zero generating a null UUID for the file system. Fix this. Test case: truncate -s 256M test.img i=0 while : do mkfs.reiser4 --force --yes --label '' test.img line=`debugfs.reiser4 test.img 2> /dev/null | egrep '^uuid:'` ((i++)) echo "[$i] $line" echo "$line" | grep -q '<none>' && break done Output fragment: [1] uuid: 17073919-e41d-4892-9b22-4294d1544c4a [2] uuid: af2821de-ea85-4f20-9621-4fbd128b3fb8 [3] uuid: c0fb805b-e224-4695-a504-d87460d158ae ... [34] uuid: b747540d-5280-4e0f-bae2-922200000000 [35] uuid: d604794d-097f-4810-bbb3-01a1518f3ef1 [36] uuid: 9634100c-1f98-42b3-a684-c9df77ab54e2 [37] uuid: <none> diff --git a/libreiser4/master.c b/libreiser4/master.c index 649434d96..825fd38d1 100644 |
Mike Fleetwood <mike.fleetwood@googlemail.com> | no | debian | upstream, https://github.com/edward6/reiser4progs/commit/44cc024f398f60adef1519426d65f3f081ee826a | 2021-03-15 |