From owner-freebsd-bugs@FreeBSD.ORG Mon May 12 05:00:30 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0065D37B401 for ; Mon, 12 May 2003 05:00:30 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DB3A43FE0 for ; Mon, 12 May 2003 05:00:29 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4CC0TUp013895 for ; Mon, 12 May 2003 05:00:29 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4CC0TEE013893; Mon, 12 May 2003 05:00:29 -0700 (PDT) Date: Mon, 12 May 2003 05:00:29 -0700 (PDT) Message-Id: <200305121200.h4CC0TEE013893@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Alex Semenyaka Subject: Re: bin/52072: Wrong behaviour of the ftpd when the OOB data received X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Alex Semenyaka List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 12:00:30 -0000 The following reply was made to PR bin/52072; it has been noted by GNATS. From: Alex Semenyaka To: Nick Leuta Cc: freebsd-gnats-submit@FreeBSD.org, alexs@ratmir.ru Subject: Re: bin/52072: Wrong behaviour of the ftpd when the OOB data received Date: Mon, 12 May 2003 15:59:46 +0400 On Mon, May 12, 2003 at 02:12:57AM +0400, Nick Leuta wrote: > There is another approach to the solution. I don't know what's better... No, it is not another approach :) This should be applied _as_ _well_. I just forgot to check if syscalls have made restartable or not. Of course they should. > This patch tries to fix a potential incomplite write() call - SIGURG signal It does not. This will help only if we are already in the syscall but no data were transferred yet. If even the only byte is passed - the write() will be interrupted. Same situation with read(). I do not remember though how about sendfile()... should be the same there. SY, Alex