Re: Ctrl+C doesn't interrupt process waiting for I/O
[Posted July 1, 2008 by corbet]
| From: |
| Alan Cox <alan-AT-lxorguk.ukuu.org.uk> |
| To: |
| Avi Kivity <avi-AT-qumranet.com> |
| Subject: |
| Re: Ctrl+C doesn't interrupt process waiting for I/O |
| Date: |
| Sun, 29 Jun 2008 13:37:57 +0100 |
| Message-ID: |
| <20080629133757.7d183385@lxorguk.ukuu.org.uk> |
| Cc: |
| Jeremy Fitzhardinge <jeremy-AT-goop.org>,
=?UTF-8?B?VMO2csO2aw==?= Edwin <edwintorok-AT-gmail.com>,
Linux Kernel <linux-kernel-AT-vger.kernel.org> |
| Archive-link: |
| Article,
Thread
|
> Applications should not assume that write() (or other syscalls) can't
> return EINTR. Not all filesystems have a bounded-time backing store.
Unix tradition (and thus almost all applications) believe file store
writes to be non signal interruptible. It would not be safe or practical
to change that guarantee.
Alan
(
Log in to post comments)
