Messages in this thread | | | From | David Woodhouse <> | Subject | Re: manipulating sigmask from filesystems and drivers | Date | Thu, 01 Aug 2002 23:29:31 +0100 |
| |
torvalds@transmeta.com said: > Any regular file IO is supposed to give you the full result.
read(2) is permitted to return -EINTR. Granted, we shouldn't allow it to be interrupted and return a partial read after the point we start to copy_to_user(), but before then it's fair game.
Regular file I/O through the page cache is inherently restartable, anyway, as long as you're careful about fpos.
There are better examples where you really can't have a cleanup path without severe pain, even using ERESTARTNOINTR, and I was only joking about removing TASK_UNINTERRUPTIBLE _entirely_ -- but the point remains that reducing its usage would be nice.
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |