Line 1: |
Line 1: |
| {{Release|2.5|15 Aug 2016}} | | {{Release|2.5|15 Aug 2016}} |
− |
| |
− | Name: Concrete oriole
| |
| | | |
| === New features === | | === New features === |
Line 7: |
Line 5: |
| ** fs.mqueue.msg*_default sysctls | | ** fs.mqueue.msg*_default sysctls |
| ** Unix sockets with overwritten paths | | ** Unix sockets with overwritten paths |
| + | ** Link-remap files in removed directories |
| | | |
| === Optimizations/improvements === | | === Optimizations/improvements === |
Line 19: |
Line 18: |
| * TCP window could remain clamped after restore resulting in connection lockup/slowdown | | * TCP window could remain clamped after restore resulting in connection lockup/slowdown |
| * Dump could stuck when injecting a parasite | | * Dump could stuck when injecting a parasite |
− | * The --timeout option wasn't taken into account when freezing tasks using freezecg | + | * The {{Opt|--timeout}} option wasn't taken into account when freezing tasks using freezecg |
| * Race in freezeing/seizing could result in lost tasks | | * Race in freezeing/seizing could result in lost tasks |
| * Memory leaks here and there on error paths | | * Memory leaks here and there on error paths |
| * Double free in xvstrcat (crash) | | * Double free in xvstrcat (crash) |
| * VDSO length was mis-calculated | | * VDSO length was mis-calculated |
− | * Symlink on --root path could make restore erroneously fail | + | * Symlink on {{Opt|--root}} path could make restore erroneously fail |
| * Potential memory corruption on reading mntns images | | * Potential memory corruption on reading mntns images |
| * When restoring on systems with low pid_max limit restore could fail | | * When restoring on systems with low pid_max limit restore could fail |