bash should probably undo O_NONBLOCK mode on stdin/stdout before reading/writing to it, for robustness reasons. zsh does this already. This was noticed in this bug, where systemd-nspawn turned O_NONBLOCK on but forgot to turn it off again: https://bugs.freedesktop.org/show_bug.cgi?id=70622 I fixed this in systemd-nspawn now, but it would be good if bash would protect itself from this, given that abnormal nspawn exits will still leave the non-block flag on.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
I initiated a discussion here https://lists.gnu.org/archive/html/bug-bash/2017-01/msg00039.html
Fixed in this bash snapshot http://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=bc371472444f900d44050414e3472f7349a7aec7
bash-4.4.12-4.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-075ed3aef8
bash-4.4.12-4.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-075ed3aef8
bash-4.4.12-4.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.