On 10/17/2012 10:44 AM, Jim Meyering wrote:
> From a5365003c88f4fce6293827c13f90acd0b5bd0cc Mon Sep 17 00:00:00 2001
> From: Jim Meyering
> Date: Tue, 16 Oct 2012 17:43:49 +0200
> Subject: [PATCH] cp: avoid data-corrupting free-memory-read
>
> * src/extent-scan.c (extent_scan_read): Reset our las
Bernhard Voelker wrote:
> On 10/17/2012 10:44 AM, Jim Meyering wrote:
...
>> ** Bug fixes
>>
>> + cp could read from freed memory and could even make corrupt copies.
>> + This could happen only with a very fragmented input file and when using
>> + its FIEMAP/extent-based copying code. [bug int
Dear Jim, dear Pádraig,
preserving the command's exit code is useful for, e.g., running solver
competitions, where competition participants have an upper bound on the
runtime for finding solutions to very hard problems.
Imagine you want to run a command which is outputting (periodically or
on-req
