Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261152AbVBQPp7 (ORCPT ); Thu, 17 Feb 2005 10:45:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261160AbVBQPp7 (ORCPT ); Thu, 17 Feb 2005 10:45:59 -0500 Received: from fire.osdl.org ([65.172.181.4]:38113 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261152AbVBQPp5 (ORCPT ); Thu, 17 Feb 2005 10:45:57 -0500 Date: Thu, 17 Feb 2005 07:45:56 -0800 (PST) From: Linus Torvalds To: "Theodore Ts'o" cc: Roman Zippel , Andreas Schwab , linux-kernel@vger.kernel.org Subject: Re: Pty is losing bytes In-Reply-To: <20050217044444.GA6115@thunk.org> Message-ID: References: <20050216144203.GB7767@thunk.org> <20050217044444.GA6115@thunk.org> 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 Content-Length: 877 Lines: 26 On Wed, 16 Feb 2005, Theodore Ts'o wrote: > > Yes, but then when the buffer is full, and we return the "we'll take > anything" return value, the code that was getting confused with the > "incorrect" receive_room value will still be getting confused.... But that's fine - at that point we're literally _supposed_ to drop characters: we have to, in order to see the EOLN. But we're only supposed to drop characters IFF: - the buffer is full - we are in canon mode - we _still_ haven't seen a single EOLN in the whole buffer If any of these three isn't true, we're not supposed to drop anything. That's my argument. Linus - 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/