Messages in this thread | | | From | Paul Menage <> | Subject | Re: manipulating sigmask from filesystems and drivers | Date | Fri, 02 Aug 2002 10:57:33 -0700 |
| |
In article <0C01A29FBAE24448A792F5C68F5EA47D2D3E2B@nasdaq.ms.ensim.com>, you write: > >With write(), you have to make a judgement call. Unlike read, a truncated >write _is_ visible outside the killed process. But exactly like read() >there _are_ system management reasons why you may really need to kill >writers. So the debatable point comes from whether you want to consider a >killing signal to be "exceptional enough" to warrant the partial write. >
How about a sysctl that lets the user specify the size threshold at which writes use a killable wait state rather than TASK_UNINTERRUPTIBLE? (Probably defaulting to never.)
Paul - 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/
| |