Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Feb 2003 22:41:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Feb 2003 22:41:01 -0500 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:12174 "EHLO lacrosse.corp.redhat.com") by vger.kernel.org with ESMTP id ; Tue, 11 Feb 2003 22:41:01 -0500 Date: Tue, 11 Feb 2003 19:50:41 -0800 Message-Id: <200302120350.h1C3ofQ19892@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Linus Torvalds X-Fcc: ~/Mail/linus Cc: Ingo Molnar , Subject: Re: another subtle signals issue In-Reply-To: Linus Torvalds's message of Tuesday, 11 February 2003 19:18:33 -0800 X-Fcc: ~/Mail/linus X-Zippy-Says: I'm EXCITED!! I want a FLANK STEAK WEEK-END!! I think I'm JULIA CHILD!! Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1046 Lines: 18 > You just have to read it in a way that says "partial results are > permissible, and are part of the normal behaviour". And then the fact that > when ^Z happens you get partial results from pipes is not "different > behaviour" from a qualitative standpoint - even though in fact we'd get a > full result if the ^Z didn't happen. I'm not talking about reading from pipes, that was your example. I was talking about calls with timeouts, like semop, whose interface do not permit partial results. Anyway, I find your reading insupportable even in reference to read or write. read and write are explicitly specified to return partial results when interrupted by a signal, and are not permitted to do so otherwise. 1003.1-2001 2.4.4 defines "interrupted" in reference only to signals that are caught. - 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/