Last year a bug was reported to upstream coreutils [1] about problems on using 'sort -u'. Until recently, there was no known reproducing process; one such process was published last week [2].
Although triggering the bug can be said to be a non-completely trivial use case, data loss in 'sort' should be looked at as a serious issue.
Today Jim Meyering committed what looks like the final touches of the fix (incidentally also solving a different issue (a free memory read), also in 'sort'. There are 4 commits affected, and they are shown starting in [3].
Given this is a data loss potential, I am opening this bug for all affected releases (this bug affects Coreutils 8.9 onwards -- Precise and Quantal). I am still to run the tests on Lucid, Natty, and Oneiric.
Last year a bug was reported to upstream coreutils [1] about problems on using 'sort -u'. Until recently, there was no known reproducing process; one such process was published last week [2].
Although triggering the bug can be said to be a non-completely trivial use case, data loss in 'sort' should be looked at as a serious issue.
Today Jim Meyering committed what looks like the final touches of the fix (incidentally also solving a different issue (a free memory read), also in 'sort'. There are 4 commits affected, and they are shown starting in [3].
Given this is a data loss potential, I am opening this bug for all affected releases (this bug affects Coreutils 8.9 onwards -- Precise and Quantal). I am still to run the tests on Lucid, Natty, and Oneiric.
[1] http:// lists.gnu. org/archive/ html/bug- coreutils/ 2011-10/ msg00057. html lists.gnu. org/archive/ html/bug- coreutils/ 2012-08/ msg00027. html lists.gnu. org/archive/ html/bug- coreutils/ 2012-08/ msg00057. html
[2] http://
[3] http://