From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964982AbbLROer (ORCPT ); Fri, 18 Dec 2015 09:34:47 -0500 Received: from smtp-out-no.shaw.ca ([64.59.134.9]:48999 "EHLO smtp-out-no.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964938AbbLROeo (ORCPT ); Fri, 18 Dec 2015 09:34:44 -0500 X-Greylist: delayed 488 seconds by postgrey-1.27 at vger.kernel.org; Fri, 18 Dec 2015 09:34:44 EST X-Authority-Analysis: v=2.1 cv=AMkI9oPf c=1 sm=1 tr=0 a=qZxK3cM5tHtOUZVZkOzy1Q==:117 a=qZxK3cM5tHtOUZVZkOzy1Q==:17 a=3I1X_3ewAAAA:8 a=kj9zAlcOel0A:10 a=pt2BBW51Tf0vaGruO30A:9 a=CjuIK1q_8ugA:10 Date: Fri, 18 Dec 2015 07:26:24 -0700 (Mountain Standard Time) From: Marc Aurele La France To: Peter Hurley cc: Greg Kroah-Hartman , Jiri Slaby , linux-kernel@vger.kernel.org, Volth , Damien Miller Subject: Re: n_tty: Check the other end of pty pair before returning EAGAIN on a read() In-Reply-To: <566AD5FC.6010407@hurleysoftware.com> Message-ID: References: <56699356.8040802@hurleysoftware.com> <566A13C2.7040803@hurleysoftware.com> <566AD5FC.6010407@hurleysoftware.com> User-Agent: Alpine 2.00 (WNT 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-CMAE-Envelope: MS4wfHiwjvgS9iyUBfcgqANKhykAjM9vQxuURhn7B/28c6SbCiIu1VzxdMcBDVnHp6nWiSJpqUVfXWkEwuWGOJb9v1b1WtOJWHfxvmNY92TWQY0lHwXPP42T UzVEdBdr6XTzu+8PQWxTPeBzrKuwsSKHwmEaeW6AReROVWxhYtLjNial+oapPMUdLoB7i1LV1JfQ2TeVtT8NBs1OixRH1ddFAyWmTn+rCwbVAf0Bk6LpDL4l YiHeDtwxB2WJ7FX2GpZxTrAWmveoBuAtdJdmUCIVEEels2ihmTYjXgGTD5/1N4jY01iW5/Pvm1GeQPm0PR3VB9S/k+PFxa22f2H11rNl5/E= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 11 Dec 2015, Peter Hurley wrote: > On 12/11/2015 05:37 AM, Marc Aurele La France wrote: >> I am not asking to read data before it has been produced. I am puzzled >> that despite knowing that the data exists, I can now be lied to when I >> try to retrieve it, when I wasn't before. We are talking about what is >> essentially a two-way pipe, not some network or serial connection with >> transmission delays userland has long experience in dealing with. >> These previously internal additional delays, that are now exposed to >> userland, are simply an implementation detail that userland did not, >> and should not, need to worry about. > > Your mental model is that pseudo-terminals are a synchronous pipe, which > is not true. > > But this argument is pointless because the regression needs to be fixed > regardless of the merits. Fair enough. Anything new on this? Thanks. Marc.