From owner-freebsd-stable@FreeBSD.ORG  Wed Jul  6 10:25:08 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E31CB16A41C
	for <freebsd-stable@freebsd.org>; Wed,  6 Jul 2005 10:25:08 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9649F43D49
	for <freebsd-stable@freebsd.org>; Wed,  6 Jul 2005 10:25:08 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk)
	by mail.ticketswitch.com with esmtp (Exim 4.50 (FreeBSD))
	id 1Dq75W-000Ids-Lm
	for freebsd-stable@freebsd.org; Wed, 06 Jul 2005 11:25:06 +0100
Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim
	4.50 (FreeBSD)) id 1Dq75W-000J4H-Av
	for freebsd-stable@freebsd.org; Wed, 06 Jul 2005 11:25:06 +0100
To: freebsd-stable@freebsd.org
Message-Id: <E1Dq75W-000J4H-Av@dilbert.firstcallgroup.co.uk>
From: Pete French <petefrench@ticketswitch.com>
Date: Wed, 06 Jul 2005 11:25:06 +0100
Subject: Interrupted system calls on 5.4
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2005 10:25:09 -0000

Since moving from 4.11 to 5.4 I have started seeing the occasional write
to a socket return with EINTR. This puzzles me, as looking at the man page
for siginterrupt it says that restarting the system call is the default
behaviour (and has been since BSD 4.2) if no data has been transferred. If
data *has* been transferred then I will simply get a short write returned.

So by my reading I should never see an EINTR in the default case - and
indeed I didn't under 4.11 - but under 5.4 I do.

Is this a failure of my understanding somewhere along the line or is there
some kind of problem here ?

-pcf.