[erlang-questions] Yaws's "sendfile" linked-in driver : "stealing control of fd" error

[Zabrane Mickael]

Hi Steve,

> Hi Sverker, I agree it's an error in the sendfile driver, but so far
> we have no evidence that it results in erroneous transfers or
> incorrect data. As I explained earlier, I've only ever seen it under
> catastrophic circumstances, but the fatal errors I saw weren't caused
> by this issue; rather, this issue was a side effect of the fatal
> errors. What Mikael is seeing, though, has nothing to do with fatal
> errors, so I think for cases like his it's just a rare and innocuous
> error report. I suspect it occurs due to the tcp driver closing the
> socket before the sendfile driver has dropped interest in it but
> that's only a guess.

That's correct. I confirm that in my case, the error occurs only when the Socket is
closed.

> I'll see if I can't come up with a way to reliably reproduce this, but
> either way it might not be fixable in the current code since the
> sendfile driver can't know if or when the tcp driver is also
> registered for the socket being writeable. Maybe this can be handled
> correctly as part of Tuncer's effort to add the sendfile functionality
> directly into Erlang/OTP.


If you need help, don't hesitate.

Regards,
Zab