https://bugzilla.mindrot.org/show_bug.cgi?id=2492
--- Comment #8 from Volth <[email protected]> --- I noticed that read() returns EAGAIN many times, openssh call read() again until it returns success (or other error). I does not cause any problem unless the heuristic is applied, I mean the line "force = c->isatty && c->detach_close && c->istate != CHAN_INPUT_CLOSED;" If there is no pty allocated - there is no problem with EAGAIN, read() returns EAGAIN, openssd retries. Until openssh get the exitcode of the child process - there is no problem with EAGAIN, read() returns EAGAIN, openssd retries. The problem is only when openssh gets the the exitcode (thus set c->detach_close to true) and only since this moment EAGAIN becomes illegal. But it happens. It happens before openssh gets the the exitcode as well it happens after openssh gets the the exitcode. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
