Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 1 Aug 2002 18:26:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 1 Aug 2002 18:26:12 -0400 Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:13302 "EHLO passion.cambridge.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 1 Aug 2002 18:26:11 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: David Woodhouse X-Accept-Language: en_GB In-Reply-To: References: To: Linus Torvalds Cc: Roman Zippel , David Howells , alan@redhat.com, linux-kernel@vger.kernel.org Subject: Re: manipulating sigmask from filesystems and drivers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Aug 2002 23:29:31 +0100 Message-ID: <11294.1028240971@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 25 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/