On Sun, 8 Jan 2023 15:39:05 +0100 наб wrote:
Control: tags -1 + fixed-upstream
Turns out it was /not/ a one-line fix, since it exposed a lot of other
latent bugs; either way, fixed upstream in this series:
https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=07cad228ae4d1567aeb6d13d2af83d0a28d13b67
https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=91a375576d37bb4db1eca48e6bf5bac0db6cc3fa
https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=5f094d08c5bcee876191404a4f3dd2d075571215
https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=44ae22beedf8a3d68bbfa1d065ad677182372de2
The issue has been raised another time on the debian-user mailing list,
so I have decided to look closer at it. Even more commits are required, see
Herbert Xu. [v3 PATCH 0/3] Improve performance when reading stdin.
Sun, 02 Jun 2024 09:31:30 +0800
https://lore.kernel.org/dash/cover.1717291846.git.herb...@gondor.apana.org.au/t/#u
The performance when reading stdin has regressed after we started
reading one byte at a time. This patch series uses lseek(2) and
tee(2) to recover performance where possible.
Accordingly to earlier commit messages, impact on performance was
considered unimportant.
I have not tried to find commits adding unit tests covering the issue.
Initially I had a hope that it may be safe to add patches to Debian
package before next dash release, but now I am less sure.
