Package: bugs.debian.org
Severity: important
Dear Maintainer,
this has a major effect on the software I use, it seems to be fundamental to
all named pipe I/O.
* What led up to the situation?
- Most software I use reading/writing to a named pipe becomes unreliable!
* What exactly did you do (or not do) that was effective (or
ineffective)?
- I tried the code that reproduces the problem below elsewhere (e.g. Debian
Wheezy, other distributions, ...) and it works fine. Not on Stretch.
* What was the outcome of this action?
- Seems broken only on Stretch, of the systems I could test. Feel free to
investigate elsewhere too.
* What outcome did you expect instead?
- Setting up and running two sides of a named pipe producer/consumer is
broken:
Side "Producer": (from a Bash instance)
rm /tmp/f; mkfifo /tmp/f; n_crashes=0; while true; do echo \
n_crashes=$n_crashes; (i=0; while true; do echo $((i++)) > /tmp/f; done); \
((n_crashes++)); done
Side "Consumer": (again, a Bash instance; a separate Bash instance)
while true; do echo $(< /tmp/f); done
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
