Messages in this thread | | | From | David Woodhouse <> | Subject | Re: wait queue process state | Date | Wed, 29 May 2002 11:58:58 +0100 |
| |
alan@lxorguk.ukuu.org.uk said: > What Unix and standards say and do make that one unfortunately a very > bad idea. Its true that to the letter of the specs you can do > interruptible disk I/O. Its also true to the real world that vast > amounts of software breaks in subtle, unreported, oh hell what ate my > file kind of ways
Broken software can be fixed.
There are few excuses for uninterruptible sleep. Most of them are 'I was too lazy to write the cleanup path.'
The one you offer seems to be 'Other people are too lazy to write the cleanup paths which POSIX mandates.' -- which isn't a great deal more acceptable than the original excuse, IMHO.
What I'd _really_ like at the moment is an option to allow read_inode() to be interruptible. Currently there's no way for it to exit without leaving a bad inode behind, which prevents the _next_ iget() for that inode from actually succeeding.
-- 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/
| |