Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 12 Apr 2001 17:58:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 12 Apr 2001 17:58:11 -0400 Received: from [216.151.155.121] ([216.151.155.121]:33287 "EHLO belphigor.mcnaught.org") by vger.kernel.org with ESMTP id ; Thu, 12 Apr 2001 17:58:03 -0400 To: Daniel Podlejski Cc: Linux Kernel List Subject: Re: Incorect signal handling ? In-Reply-To: <20010412223128.A11625@witch.underley.eu.org> From: Doug McNaught Date: 12 Apr 2001 17:56:37 -0400 In-Reply-To: Daniel Podlejski's message of "Thu, 12 Apr 2001 22:31:28 +0200" Message-ID: Lines: 21 User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/21.1 (20 Minutes to Nikko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Daniel Podlejski writes: > Hi, > > there is litlle programm: > > signal (SIGALRM, empty); > alarm (1); > > a = read(fd, buf, 511); > > while (a && a != -1) a = read(fd, buf, 511); > I open /tmp/nic and run compiled program. > There should be error EINTR in read, but isn't. "Fast" system calls (eg reads from disk) are generally uninterruptible; thus the signal will be deferred until the read() returns. -Doug - 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/