Message235092
| Author |
vstinner |
| Recipients |
ned.deily, neologix, pitrou, vstinner |
| Date |
2015年01月31日.09:35:20 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAMpsgwYjNs5uG8t8YYPZDQ_0aYQBWtvfyYBDzYg=Syw_BJTD1g@mail.gmail.com> |
| In-reply-to |
<CAH_1eM27g7JUw8W_+QEE24WO8hHqDKYUWDvZ5Qgtx6Mkt8ASWw@mail.gmail.com> |
| Content |
Charles-François Natali added the comment:
> I just realized I didn't retry upon EINTR for open(): eintr-4.diff
> adds this, along with tests (using a fifo).
>
> Also, I added comments explaining why we don't retry upon close() (see
> e.g. http://lwn.net/Articles/576478/ and
> http://linux.derkeiler.com/Mailing-Lists/Kernel/2005-09/3000.html).
I didn't read these articles yet, but I will. IMO the PEP must be
updated if we don't retry in close(), since close() is used as an
example where "EINTR is unexpected"! |
|