lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 28 Jun 2008 22:13:54 -0700 From: Jeremy Fitzhardinge <jeremy@...p.org> To: Avi Kivity <avi@...ranet.com> CC: Török Edwin <edwintorok@...il.com>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: Ctrl+C doesn't interrupt process waiting for I/O Avi Kivity wrote: >> >> Yes, it's intended behaviour. Filesystem IO syscalls are considered >> "fast" and are interruptible. Usermode code can reasonably expect >> that file IO will never return EINTR. > > That's filesystem dependent; if you mount an nfs filesystem with the > 'intr' mount option, it will be interruptible (which makes sense, as > it is impossible to guarantee the server's responsiveness). 'intr' is a pretty bad idea, and I would never recommend it ('soft' is better). It's an excellent way to destroy data when a stray signal causes a syscall to fail with EINTR in an unexpected way (write being the obvious one, but link, unlink, truncate or even close can fail in odd ways can cause havok). I don't know of any other filesystem with a similarly bad option. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists