tee: do not retry on EINTR#12505
Conversation
b35b6a7 to
b78b745
Compare
Merging this PR will not alter performance
Comparing Footnotes
|
This comment was marked as duplicate.
This comment was marked as duplicate.
| s.write_all(buf)?; | ||
| // needs unsafe to remove buffering... flush after write_all to keep overhead minimal | ||
| s.flush() | ||
| let mut buf = buf; |
This comment was marked as resolved.
This comment was marked as resolved.
Yeah, might be a good idea. Will close the PR and research the issue |
|
|
|
Are you planning to tackle this yourself then? |
This comment was marked as outdated.
This comment was marked as outdated.
|
GNU testsuite comparison: |
|
I think there is no compatibility requirement for non-unix. But does EINTR exist on Windows? |
This comment was marked as resolved.
This comment was marked as resolved.
223039b to
44a6430
Compare
Sorry, got things a little messy here and accidentally changed that. Just fixed it |
|
Thanks. It is my mistake. |
1de19a6 to
85a6062
Compare
|
I noticed that there is . |
|
Doesn't seem to be an issue, |
Related to #12469
Writer::write_allwas delegating to the standard library'swrite_all, which unconditionally retries on EINTR.Replaces the
write_alldelegation with a manual loop that callswrite()directly and propagatesEINTRimmediately without retrying.